Skip to content

Commit bb0b50f

Browse files
committed
Add hyper-link for Item 57: Consider interactive debugging with pdb
1 parent b1b24dd commit bb0b50f

File tree

1 file changed

+9
-2
lines changed

1 file changed

+9
-2
lines changed

README.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -163,7 +163,7 @@ Python 3.
163163
### [Item 17: Be defensive when iterating over arguments](item_17_be_defensive.py)
164164
- 1. Beware of functions that iterate over input arguments multiple times. If
165165
these arguments are iterators, you may see strange behavior and missing
166-
- values.
166+
values.
167167
- 2. Python's iterator protocol defines how containers and iterators interact
168168
with the iter and next built-in functions, for loops, and related
169169
expression.
@@ -572,7 +572,14 @@ Python 3.
572572
integration tests (for modules that interact).
573573

574574

575-
### []()
575+
### [Item 57: Consider interactive debugging with pdb](item_57_pdb.py)
576+
1. You can initiate the Python interactive debugger at a point of interest
577+
directly in your program with the import pdb; pdb.set_trace() statements.
578+
2. The Python debugger prompt is a full Python shell that lets you inspect
579+
and modify the state of a running program.
580+
3. pdb shell commands let you precisely control program execution, allowing
581+
you to alternate between inspecting program state and progressing program
582+
execution.
576583

577584

578585
### []()

0 commit comments

Comments
 (0)