Skip to content

Commit

Permalink
bpo-28546: [doc] Clarify setting pdb breakpoints (GH-30360)
Browse files Browse the repository at this point in the history
Co-authored-by: Ian Kelling <ian@iankelling.org>
(cherry picked from commit 6d07a9f)

Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
  • Loading branch information
miss-islington and hugovk committed Jan 7, 2022
1 parent c55616c commit a74eb54
Showing 1 changed file with 4 additions and 5 deletions.
9 changes: 4 additions & 5 deletions Doc/library/pdb.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit a74eb54

Please sign in to comment.