Lines Matching refs:breakpoint

80    The built-in :func:`breakpoint()`, when called with defaults, can be used
134    a breakpoint at a given point in a program, even if the code is not
281    to specify a breakpoint in another file (probably one that hasn't been loaded
282    yet).  The file is searched on :data:`sys.path`.  Note that each breakpoint
283    is assigned a number to which all the other breakpoint commands refer.
286    true before the breakpoint is honored.
288    Without argument, list all breaks, including for each breakpoint, the number
289    of times that breakpoint has been hit, the current ignore count, and the
294    Temporary breakpoint, which is removed automatically when it is first hit.
300    With a space separated list of breakpoint numbers, clear those breakpoints.
305    Disable the breakpoints given as a space separated list of breakpoint
306    numbers.  Disabling a breakpoint means it cannot cause the program to stop
307    execution, but unlike clearing a breakpoint, it remains in the list of
316    Set the ignore count for the given breakpoint number.  If count is omitted,
317    the ignore count is set to 0.  A breakpoint becomes active when the ignore
319    breakpoint is reached and the breakpoint is not disabled and any associated
324    Set a new *condition* for the breakpoint, an expression which must evaluate
325    to true before the breakpoint is honored.  If *condition* is absent, any
326    existing condition is removed; i.e., the breakpoint is made unconditional.
330    Specify a list of commands for breakpoint number *bpnumber*.  The commands
339    To remove all commands from a breakpoint, type ``commands`` and follow it
342    With no *bpnumber* argument, ``commands`` refers to the last breakpoint set.
344    You can use breakpoint commands to start your program up again.  Simply use
354    breakpoint—which could have its own command list, leading to ambiguities about
358    stopping at a breakpoint is not printed.  This may be desirable for breakpoints
360    commands print anything, you see no sign that the breakpoint was reached.
393    Continue execution, only stop when a breakpoint is encountered.