profile.runctx()
  • References/Python/Python/Debugging & Profiling

profile.runctx(command, globals, locals, filename=None) This function is similar to run(), with added arguments

2025-01-10 15:47:30
bdb.Bdb.get_breaks()
  • References/Python/Python/Debugging & Profiling

get_breaks(filename, lineno) Return all breakpoints for lineno in filename, or an empty list if none are set

2025-01-10 15:47:30
pstats.Stats.strip_dirs()
  • References/Python/Python/Debugging & Profiling

strip_dirs() This method for the Stats class removes all leading path information from file names. It is very useful

2025-01-10 15:47:30
pdb.Pdb.set_trace()
  • References/Python/Python/Debugging & Profiling

set_trace() See the documentation for the functions explained above.

2025-01-10 15:47:30
bdb.Breakpoint.disable()
  • References/Python/Python/Debugging & Profiling

disable() Mark the breakpoint as disabled.

2025-01-10 15:47:30
profile.Profile.print_stats()
  • References/Python/Python/Debugging & Profiling

print_stats(sort=-1) Create a Stats object based on the current profile and print the results to stdout.

2025-01-10 15:47:30
bdb.Bdb.clear_break()
  • References/Python/Python/Debugging & Profiling

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

2025-01-10 15:47:30
tracemalloc.clear_traces()
  • References/Python/Python/Debugging & Profiling

tracemalloc.clear_traces() Clear traces of memory blocks allocated by Python. See also stop()

2025-01-10 15:47:30
bdb.Bdb.break_here()
  • References/Python/Python/Debugging & Profiling

break_here(frame) This method checks if there is a breakpoint in the filename and line belonging to frame or, at least

2025-01-10 15:47:30
pdb.Pdb.runeval()
  • References/Python/Python/Debugging & Profiling

runeval(expression, globals=None, locals=None) runcall(function, *args, **kwds) set_trace()

2025-01-10 15:47:30