I wanted to ask here before I opened an issue in case this is already implemented. Is there a way to make PuDB hit breakpoints without putting a set_trace, or using the pudb entry point script? I want something like
pudb.set_trace(stop=False) that I can put in the main() of my program, that will act just like set_trace() and an immediate 'c'. If such a thing doesn't exist, do you think that set_interrupt_handler should do this (and even if it does, do you think it should)? Sometimes it feels annoying that you have to get pudb sufficiently "primed" to make it stop at breakpoints. Also, what are the disadvantages of running code "through" PuDB (i.e., set_trace and then 'c'), as opposed to independently of it? Is it sufficiently slower? Aaron Meurer _______________________________________________ Pudb mailing list [email protected] http://lists.tiker.net/listinfo/pudb
