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

Fri Jan 7 14:41:40 EST 2022

https://github.com/python/cpython/commit/6d07a9fb7cb31433c376a1aa20ea32001da0a418
commit: 6d07a9fb7cb31433c376a1aa20ea32001da0a418
branch: main
author: Hugo van Kemenade <hugovk at users.noreply.github.com>
committer: iritkatriel <1055913+iritkatriel at users.noreply.github.com>
date: 2022年01月07日T19:41:23Z
summary:
bpo-28546: [doc] Clarify setting pdb breakpoints (GH-30360)
Co-authored-by: Ian Kelling <ian at iankelling.org>
files:
M Doc/library/pdb.rst

diff --git a/Doc/library/pdb.rst b/Doc/library/pdb.rst
index 6d1dba1bf2eb0..ca59576336bf8 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
