Skip to content

Commit ed2656a

Browse files
bpo-28546: [doc] Clarify setting pdb breakpoints (GH-30360)
Co-authored-by: Ian Kelling <[email protected]> (cherry picked from commit 6d07a9f) Co-authored-by: Hugo van Kemenade <[email protected]>
1 parent 75a1865 commit ed2656a

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

Doc/library/pdb.rst

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -67,14 +67,13 @@ useful than quitting the debugger upon program's exit.
6767
before the first line of the module.
6868

6969

70-
The typical usage to break into the debugger from a running program is to
71-
insert ::
70+
The typical usage to break into the debugger is to insert::
7271

7372
import pdb; pdb.set_trace()
7473

75-
at the location you want to break into the debugger. You can then step through
76-
the code following this statement, and continue running without the debugger
77-
using the :pdbcmd:`continue` command.
74+
at the location you want to break into the debugger, and then run the program.
75+
You can then step through the code following this statement, and continue
76+
running without the debugger using the :pdbcmd:`continue` command.
7877

7978
.. versionadded:: 3.7
8079
The built-in :func:`breakpoint()`, when called with defaults, can be used

0 commit comments

Comments
 (0)