I am starting to use pudb to debug Python. This is normal, and I can go through, and it stops at the breakpoints that I entered into the code using pudb.set_trace (). So far, so good. The main problem I am having is the following:
If I hit ^ X to go to the command line panel, I can type executable lines or variable names, for example, run interactive Python, but the slightest typo (or an experiment looking for other commands or a request for help ()) lands me in a state from which I can’t recover. Even Control-c (as stated in https://docs.python.org/2/tutorial/appendix.html#tut-interac ) simply displays as “^ C” and does nothing.
For example, if I type "help ()", it prints some Python help (not pudb), redisplays "help ()" in yellow, and then I'm dead in the water. Backspace will not affect the displayed "help ()", and ^ H just displays as a caret + H - until I go back when it seems to be added to "help ()" as a literal backspace, so how can i remove the part of "help ()". I can type something after "help ()", but I always get:
SyntaxError: unexpected EOF while parsing
and then re-display what I typed. How can I clear this state and return to the normal command line without waiting for the terminal program to finish?
Using a terminal on Mac OS X 10.9.5, although I can also try Linux.