From ed2656a7d313dd9fa3a963d8b4dca4438cf73bc9 Mon Sep 17 00:00:00 2001 From: "Miss Islington (bot)" <31488909+miss-islington@users.noreply.github.com> Date: Fri, 7 Jan 2022 12:03:36 -0800 Subject: bpo-28546: [doc] Clarify setting pdb breakpoints (GH-30360) Co-authored-by: Ian Kelling (cherry picked from commit 6d07a9fb7cb31433c376a1aa20ea32001da0a418) Co-authored-by: Hugo van Kemenade --- Doc/library/pdb.rst | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/Doc/library/pdb.rst b/Doc/library/pdb.rst index ed1e971..13e1a19 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 -- cgit v0.12