bdb.Bdb.clear_break()

clear_break(filename, lineno) Delete the breakpoints in filename and lineno. If none were set, an error message is returned.

bdb.Bdb.clear_bpbynumber()

clear_bpbynumber(arg) Delete the breakpoint which has the index arg in the Breakpoint.bpbynumber. If arg is not numeric or out of range, return an error message.

bdb.Bdb.clear_all_file_breaks()

clear_all_file_breaks(filename) Delete all breakpoints in filename. If none were set, an error message is returned.

bdb.Bdb.clear_all_breaks()

clear_all_breaks() Delete all existing breakpoints.

bdb.Bdb.canonic()

canonic(filename) Auxiliary method for getting a filename in a canonical form, that is, as a case-normalized (on case-insensitive filesystems) absolute path, stripped of surrounding angle brackets.

bdb.Bdb.break_here()

break_here(frame) This method checks if there is a breakpoint in the filename and line belonging to frame or, at least, in the current function. If the breakpoint is a temporary one, this method deletes it.

bdb.Bdb.break_anywhere()

break_anywhere(frame) This method checks if there is a breakpoint in the filename of the current frame.

bdb.Bdb

class bdb.Bdb(skip=None) The Bdb class acts as a generic Python debugger base class. This class takes care of the details of the trace facility; a derived class should implement user interaction. The standard debugger class (pdb.Pdb) is an example. The skip argument, if given, must be an iterable of glob-style module name patterns. The debugger will not step into frames that originate in a module that matches one of these patterns. Whether a frame is considered to originate in a certain modu

BaseException.with_traceback()

with_traceback(tb) This method sets tb as the new traceback for the exception and returns the exception object. It is usually used in exception handling code like this: try: ... except SomeException: tb = sys.exc_info()[2] raise OtherException(...).with_traceback(tb)

BaseException.args

args The tuple of arguments given to the exception constructor. Some built-in exceptions (like OSError) expect a certain number of arguments and assign a special meaning to the elements of this tuple, while others are usually called only with a single string giving an error message.