Mirror
/
cpython
mirror of https://github.com/python/cpython
4
1
Fork 0
Code Issues Releases Wiki Activity

bpo-28546: [doc] Clarify setting pdb breakpoints (GH-30360) 

Co-authored-by: Ian Kelling <ian@iankelling.org>
This commit is contained in:
Hugo van Kemenade 2022-01-07 21:41:23 +02:00 committed by GitHub
parent 273cb8e757
commit 6d07a9fb7c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
Doc/library/pdb.rst
View File

@ -67,14 +67,13 @@ useful than quitting the debugger upon program's exit.
before the first line of the module.
The typical usage to break into the debugger from a running program is to
insert ::
The typical usage to break into the debugger is to insert::
import pdb; pdb.set_trace()
at the location you want to break into the debugger. You can then step through
the code following this statement, and continue running without the debugger
using the :pdbcmd:`continue` command.
at the location you want to break into the debugger, and then run the program.
You can then step through the code following this statement, and continue
running without the debugger using the :pdbcmd:`continue` command.
.. versionadded:: 3.7
The built-in :func:`breakpoint()`, when called with defaults, can be used