Here's the revision I just made for pydb's documentation (in
CVS). I welcome suggestions for improvement.
set_trace([cmdfile=None])
Enter the debugger before the statement which follows (in
execution) the set_trace() statement. This hard-codes a call to
the debugger at a given point
"Diez B. Roggisch" <[EMAIL PROTECTED]> writes:
> > the code works with no problem, I am playing around with the pdb, i.e
> >
> > from pdb import *
> > set_trace() for i in range(1,50):
> > print i
> > print "tired of this"
> > print "I am out"
> >
> > [EMA
Gary Wessle <[EMAIL PROTECTED]> writes:
> Hi
>
> using the debugger, I happen to be on a line inside a loop, after
> looping few times with "n" and wanting to get out of the loop to the
> next line, I set a break point on a line after the loop structure and
> hit c, that does not continue out of
> the code works with no problem, I am playing around with the pdb, i.e
>
>
> from pdb import *
> set_trace()
>
> for i in range(1,50):
> print i
> print "tired of this"
> print "I am out"
>
>
> [EMAIL PROTECTED]:~/python/practic$ python practic.py
>>
"Paul McGuire" <[EMAIL PROTECTED]> writes:
> "Gary Wessle" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> > Hi
> >
> > using the debugger, I happen to be on a line inside a loop, after
> > looping few times with "n" and wanting to get out of the loop to the
> > next line, I set a
"Gary Wessle" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi
>
> using the debugger, I happen to be on a line inside a loop, after
> looping few times with "n" and wanting to get out of the loop to the
> next line, I set a break point on a line after the loop structure and
> hit c
Hi
using the debugger, I happen to be on a line inside a loop, after
looping few times with "n" and wanting to get out of the loop to the
next line, I set a break point on a line after the loop structure and
hit c, that does not continue out of the loop and stop at the break
line, how is it down,
