That's perfect - and removing the "breakpoint" is not an issue for me
as it is normally conditional on a debug level, which I can change
from pydb
if debuglvl>3:
import pydb
pydb.set_trace()
'in XXX: c to continue'
The text line is a useful prompt
(The example here is for pydb which
bdb112 wrote:
> After a while programming in python, I still don't know how to break
> out to the debugger other than inserting an instruction to cause an
> exception.
> x=1/0
>
> In IDL one woudl write
>
> stop,'reason for stopping...'
> at which point you can inspect locals (as in pdb) and con
After a while programming in python, I still don't know how to break
out to the debugger other than inserting an instruction to cause an
exception.
x=1/0
In IDL one woudl write
stop,'reason for stopping...'
at which point you can inspect locals (as in pdb) and continue (but
you can't with pdb if
After a while programming in python, I still don't know how to break
out to the debugger other than inserting an instruction to cause an
exception.
x=1/0
In IDL one woudl write
stop,'reason for stopping...'
at which point you can inspect locals (as in pdb) and continue (but
you can't with pdb if
