Is It Possible To Remove A Break Point Set With Ipdb.set_trace()?

I used ipdb.set_trace() somewhere in my Python code. Is it possible to ignore this break point using a IPDB command? clear tells me that it cleared all break points, but IPDB stops

Solution 1:

Well, you CAN take advantage of the fact that anything in Python is an object. While in the debugger, you can do something like this:

def f(): pass
ipdb.set_trace = f

set_trace will still be called, but it won't do anything. Of course, it's somewhat permanent, but you can just do

reload ipdb

and you'll get the original behaviour back.

(why would you do this? when you accidentally put a breakpoint in an often-called function that is usually called under a try/except. Once you realize you're stopping 1000 times in this function, you try to ctrl-c, but that gets caught by the try/except and you're back in ipdb again. So, if you're in low-level code, make sure your set_traces have some context:

if myvar in ['some', 'sentinel', 'values']:
    ipdb.set_trace()

etc.

Solution 2:

After learning from Corley

ipdb.set_trace = lambda: None

Works for me.

Solution 3:

Based on Corley and GLaDOS answers, you can use this trick to set_trace for several loops without overwriting the ipdb.set_trace()

import ipdb
dbg1 = ipdb.set_trace  # BREAKPOINTfor i inrange(10):
    my_var2 = 10 / 3
    dbg1()  # BREAKPOINT
    dbg1 = lambda: Noneprint(my_var2)


dbg2 = ipdb.set_trace  # BREAKPOINTfor i inrange(10):
    my_var2 = 20 / 3
    dbg2()  # BREAKPOINT
    dbg2 = lambda: Noneprint(my_var2)

Works for me like a charm.

Solution 4:

Running the program should also tell you exactly where you've set your idb.set_trace() when it's being hit (otherwise, try the where or bt commands). You can then remove that line from the file, and restart the program.

Otherwise, you might find this useful, if you feel more experimental.