You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After it gets corrupted, it looks like Pudb is not getting any events. If I press for example CTRL-X, it just prints ^X in console. If I press Enter then, it goes to code window but still I cant see it because of drawing issues (but I know it does go to code because I'm able to press Q and Enter to exit from debugger).
After some investigations I found that importing readline module at the top of debugger.py file fixes the issue (I found it because going to ipython console was fixing the issue, so step by step I found that this is somehow fixing the issue).
So, easy fix is to add import readline, but its indirect solution.
The text was updated successfully, but these errors were encountered:
Pudb relies on something called the alternate screen to be supported in your
terminal. From your screenshot, it does not look like that's the case. What
terminal emulator are you using?
When debugger window is opened, after I go to console and I try to type something, I'm getting issues like this:
http://i.imgur.com/zPjyAMP.png
After it gets corrupted, it looks like Pudb is not getting any events. If I press for example CTRL-X, it just prints ^X in console. If I press Enter then, it goes to code window but still I cant see it because of drawing issues (but I know it does go to code because I'm able to press Q and Enter to exit from debugger).
After some investigations I found that importing readline module at the top of debugger.py file fixes the issue (I found it because going to ipython console was fixing the issue, so step by step I found that this is somehow fixing the issue).
So, easy fix is to add import readline, but its indirect solution.
The text was updated successfully, but these errors were encountered: