There is an ipdb project which embeds iPython into the standard pdb, so you can just do: import ipdb; ipdb.set_trace() It’s installable via the usual pip install ipdb. ipdb is pretty short, so instead of easy_installing you can also create a file ipdb.py somewhere on your Python path and paste the following into the file: … Read more
Even better than remembering to use -s is to use the set_trace variant that comes with Nose. Add from nose.tools import set_trace; set_trace() wherever you’d like to break in to the debugger. The stdin/out redirection will be taken care of for you. The only strange side effect I’ve run into is the inability to restart … Read more
Try the until statement. Go to the last line of the loop (with next or n) and then use until or unt. This will take you to the next line, right after the loop. http://www.doughellmann.com/PyMOTW/pdb/ has a good explanation
it’s real simple: put an assert 0 where you want to start debugging in your code and run your tests with: py.test –pdb done 🙂 Alternatively, if you are using pytest-2.0.1 or above, there also is the pytest.set_trace() helper which you can put anywhere in your test code. Here are the docs. It will take … Read more
Use an exclamation mark ! before a statement to have it run : python -m pdb test.py > /home/user/test.py(1)<module>() -> print(‘foo’) (Pdb) !n = 77 (Pdb) !n 77 (Pdb) n foo > /home/user/test.py(2)<module>() -> print(‘bar’) (Pdb) The docs say: ! statement Execute the (one-line) statement in the context of the current stack frame. The exclamation … Read more
You can run your program into pdb from the command line by running python -m pdb your_script.py It will break on the 1st line, then you’ll be able to add a breakpoint wherever you want in your code using the break command, its syntax is: b(reak) [[filename:]lineno | function[, condition]] It is flexible enough to … Read more
You can use ipdb inside jupyter with: from IPython.core.debugger import Tracer; Tracer()() Edit: the functions above are deprecated since IPython 5.1. This is the new approach: from IPython.core.debugger import set_trace Add set_trace() where you need a breakpoint. Type help for ipdb commands when the input field appears.
continue should “Continue execution, only stop when a breakpoint is encountered”, so you’ve got a breakpoint set somewhere. To remove the breakpoint (if you inserted it manually): (Pdb) break Num Type Disp Enb Where 1 breakpoint keep yes at /path/to/test.py:5 (Pdb) clear 1 Deleted breakpoint 1 (Pdb) continue Or, if you’re using pdb.set_trace(), you can … Read more
What about ipdb.set_trace() ? In your code : import ipdb; ipdb.set_trace() update: now in Python 3.7, we can write breakpoint(). It works the same, but it also obeys to the PYTHONBREAKPOINT environment variable. This feature comes from this PEP. This allows for full inspection of your code, and you have access to commands such as … Read more
You could do this while in pdb to launch a temporary interactive Python session with all the local variables available: (pdb) !import code; code.interact(local=vars()) Python 2.6.5 (r265:79063, Apr 16 2010, 13:57:41) [GCC 4.4.3] on linux2 Type “help”, “copyright”, “credits” or “license” for more information. (InteractiveConsole) >>> When you’re done, use Ctrl-D to return to the … Read more