Exercise 3: A Conditional Breakpoint in a Loop — Possible Solution
====================================================================

STEPS
------------------------------
1. Write a loop with at least 10 iterations:

for i in range(15):
    doubled = i * 2
    print(doubled)

2. Click in the gutter next to the "doubled = i * 2" line to set a
   normal breakpoint first.
3. Right-click the red breakpoint dot and choose "Edit Breakpoint"
   (per this chapter's own description of that menu option).
4. An inline input box appears. Enter the condition:
       i == 7
5. Press Enter. The breakpoint's icon changes shape slightly
   (typically to a dot with an equals-sign-like marker), indicating
   it's now a CONDITIONAL breakpoint rather than a plain one.
6. Press F5 to start debugging.
7. Watch the Variables panel (or add "i" to the Watch panel) as
   execution proceeds — the debugger runs straight through iterations
   where i is 0 through 6, WITHOUT pausing, then finally pauses when
   i reaches 7.

WHY THIS WORKS AS AN ANSWER
------------------------------
Editing an existing breakpoint to add a condition reuses this
chapter's own exact described workflow — right-click, "Edit
Breakpoint," enter a boolean condition — rather than some separate,
different mechanism.

Confirming the debugger runs THROUGH iterations 0-6 without pausing,
and only stops at i == 7, is the direct proof the condition is being
evaluated on every single iteration but only actually halting
execution when it's true — exactly the chapter's own stated use case:
"useful inside a loop where you only care about one specific
iteration, not every single pass." Without the condition, a plain
breakpoint on this line would pause 15 separate times, once per
iteration, requiring pressing Continue (F5) repeatedly to reach
iteration 7 — the conditional version reaches the same point in one
step.