diff options
| author | Hugo van Kemenade <hugovk@users.noreply.github.com> | 2022-01-07 19:41:23 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-01-07 19:41:23 (GMT) |
| commit | 6d07a9fb7cb31433c376a1aa20ea32001da0a418 (patch) | |
| tree | 75dc56899edc5bae1e9e5c07d4ead33315b0ccfa | |
| parent | 273cb8e7577d143830404f6779946a0bedb58758 (diff) | |
| download | cpython-6d07a9fb7cb31433c376a1aa20ea32001da0a418.zip cpython-6d07a9fb7cb31433c376a1aa20ea32001da0a418.tar.gz cpython-6d07a9fb7cb31433c376a1aa20ea32001da0a418.tar.bz2 | |
bpo-28546: [doc] Clarify setting pdb breakpoints (GH-30360)
Co-authored-by: Ian Kelling <ian@iankelling.org>
| -rw-r--r-- | Doc/library/pdb.rst | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/Doc/library/pdb.rst b/Doc/library/pdb.rst index 6d1dba1..ca59576 100644 --- a/Doc/library/pdb.rst +++ b/Doc/library/pdb.rst @@ -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 |