31

I'm not sure if what I'm asking is possible at all, but since python is an interpreter it might be. I'm trying to make changes in an open-source project but because there are no types in python it's difficult to know what the variables have as data and what they do. You can't just look up the documentation on the var's type since you can't be sure what type it is. I want to drop to the terminal so I can quickly examine the types of the variables and what they do by typing help(var) or print(var). I could do this by changing the code and then re-running the program each time but that would be much slower.

Let's say I have a program:

def foo():
    a = 5
    my_debug_shell()
    print a

foo()

my_debug_shell is the function I'm asking about. It would drop me to the '>>>' shell of the python interpreter where I can type help(a), and it would tell me that a is an integer. Then I type 'a=7', and some 'continue' command, and the program goes on to print 7, not 5, because I changed it.

Improve this question
1

7 Answers 7

Reset to default
42

http://docs.python.org/library/pdb.html

import pdb
pdb.set_trace()
Improve this answer
Sign up to request clarification or add additional context in comments.

4 Comments

This is clean, but requires twice as many lines as the one-liner approach that consists in generating an exception which is automatically caught by the debugger. :)
@EOL it does, however, ensure that you don't forget to turn on the debugger when running the program.
The same thing with the IPython debugger is even more convenient (replace pdb with ipdb).
After the program breaks, you are put into an interactive debugger (with the prompt (Pdb) ). Enter the command interact to be put into the Python shell (with the prompt >>> ). Enter ? in the debugger to see all available debugger commands.
33

Here is a solution that doesn't require code changes:

python -m pdb prog.py <prog_args>
(pdb) b 3
Breakpoint 1 at prog.py:3
(pdb) c
...
(pdb) p a
5
(pdb) a=7
(pdb) ...

In short:

  • start your program under debugger control
  • set a break point at a given line of code
  • let the program run up to that point
  • you get an interactive prompt that let's you do what you want (type 'help' for all options)
Improve this answer

5 Comments

That's what I was trying to describe with my answer.
@Matthew I thought as much, but wanted to provide more detail and make explicit that you don't have to change the code you're debugging.
+1: Even though this approach requires explicit line numbers (as opposed to a '1/0' exception-raising breakpoint), it indeed has the advantage of not requiring any modification of the original code.
Where/how do you set breakpoint with this method? I'm confused.
@David Just see the code sample above: python -m pdb ... starts the program under debugger control, b <line number> sets the breakpoint. Type help at the debugger promt for all commands.
13

Python 3.7+ has a new builtin way of setting breakpoints.

breakpoint()

The implementation of breakpoint() will import pdb and call pdb.set_trace().

Remember to include the braces (), since breakpoint is a function, not a keyword.

Improve this answer

Comments

10

A one-line partial solution is simply to put 1/0 where you want the breakpoint: this will raise an exception, which will be caught by the debugger. Two advantages of this approach are:

  • Breakpoints set this way are robust against code modification (no dependence on a particular line number);

  • One does not need to import pdb in every program to be debugged; one can instead directly insert "breakpoints" where needed.

In order to catch the exception automatically, you can simply do python -m pdb prog.py… and then type c(ontinue) in order to start the program. When the 1/0 is reached, the program exits, but variables can be inspected as usual with the pdb debugger (p my_var). Now, this does not allow you to fix things and keep running the program. Instead you can try to fix the bug and run the program again.

If you want to use the powerful IPython shell, ipython -pdb prog.py… does the same thing, but leads to IPython's better debugger interface. Alternatively, you can do everything from within the IPython shell:

  • In IPython, set up the "debug on exception" mode of IPython (%pdb).
  • Run the program from IPython with %run prog.py…. When an exception occurs, the debugger is automatically activated and you can inspect variables, etc.

The advantage of this latter approach is that (1) the IPython shell is almost a must; and (2) once it is installed, debugging can easily be done through it (instead of directly through the pdb module). The full documentation is available on the IPython pages.

Improve this answer

3 Comments

I also saw that there is a way to embed a call to IPython in the source code: from IPython.Shell import IPShellEmbed ipshell = IPShellEmbed() ipshell() # this call anywhere in your program will start IPython
@EOL, the first approach is interesting but when I tried it, the debugger catch the exception then exit python if I use 'python proj.py'. If I use python -m pdb prog.py, then it stops at the first line. How this 1/0 breakpoint helps on debugging?
Good question. I added two important points for the -m pdboption: (1) one must type "c" to start the program and (2) the program aborts when there is an exception but you can still have a look at the variables and try to figure out what is going on.
2

You can run the program using pdb, and add breakpoints before starting execution.

In reality though, it's usually just as fast to edit the code and put in the set_trace() call, as another user stated.

Improve this answer

Comments

1

Within an active debugger session (e.g. your programm has already reached a breakpoint, wherever it might be) enter b /path/to/my/awsome/programm.py:<line number>. This will set a break point at the given line. For example b /path/to/my/awsome/programm.py:87 results in Breakpoint 1 at /path/to/my/awsome/programm.py:87. Now enter c to continue the program execution until the next breakpoint. It seems to work only with absolute paths (beginning with /)

Improve this answer

Comments

0

Not sure what the real question is. Python gives you the 'pdb' debugger (google yourself) and in addition you can add logging and debug output as needed.

Improve this answer

1 Comment

Hi, I've edited my question. I hope this explains what I'm looking after. Is it possible?

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.