Exiting Python Debugger ipdb

Question

I use ipdb fairly often in a way to just jump to a piece of code that is isolated i.e. it is hard to write a real script that uses it. Instead I write a minimal test case with mocking and jump into it.

Exemplary for the workflow:

def func():
   ...
   import ipdb
   ipdb.set_trace()
   ...

def test_case():
    ...
    func()
    ...

Then, invoke

py.test test_file.py -s -k test_case

Now, usually I just check one variable or two, and then want to quit. Change the code and do it over again.

How do I quit? The manual says q quits the debugger. It doesn’t (really). You have to quit a few times before the debugger actually terminates. The same behavior for Ctrl-C and Ctrl-D (with the additional frustration that hitting Ctrl-D several times eventually quits the terminal, too).

Is there a smart way to force quit? Is this workflow even sensible? What is the standard way to do it?

Asked By: Joachim

||

Source

Answer 1

I put the following in my .pdbrc

import os

alias kk os.system('kill -9 %d' % os.getpid())

kk kills the debugger and (the process that trigger the debugger).

Answered By: Joachim

Answer 2

The following worked for me:

import sys
sys.exit()

On newer versions of ipython, as mentioned above and below, this doesn’t work.
In that case,

import os
os._exit(0)

should still do the trick.

Answered By: KDN

Answer 3

It’s the problem with the recent version of IPython 5.1.0. You can check with your environment using the following code:

pip freeze | egrep -i '^i'

It will be resolved by downgraded to IPython==5.0.0.

pip install ipython==5.0.0

That works for me.

Answered By: Scofield77

Answer 4

As mentioned in another answer, this was a bug in IPython 5.1. It was fixed in this pull request and is no longer an issue from IPython 5.2 and onwards. You can now use q, quit(), or Ctrl+d to exit the debugger.

Answered By: joelostblom

Answer 5

Sloppy but effective way is to set monkey patch ipdb.set_trace = lambda:0, then every subsequent time ipdb.set_trace is hit it will do nothing and return to the calling function. So you won’t have to type q any more.

Answered By: JnBrymn

Answer 6

I’ve found these solutions only succeed in breaking your kernel, and then you have to restart and load everything again.

The problem I was having was in a for loop q will just proceed to the next iteration instead of quitting out of the loop. Eventually I figured out it only happens if your for loop is in a try statement. Remove the try and you can quit out of the debugger again without it continuing the for loop.

Answered By: John Sakon

Exiting Python Debugger ipdb

Question:

Answers: