Autoreload in VS Code Python Debugger Does Not Reflect Code Changes After Breakpoint

Offen

#821 erstellt am 07.10.2025 1 Kommentar 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@eleanorjboyd arbeitet bereits daran.

Seit 16.10.2025.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

triage-needed

Description

I’m trying to use the autoreload feature described in here to enable a dynamic, interactive debugging experience.

Goal:

Allow users to modify code after hitting a breakpoint—before those lines have executed—and have those changes reflected in the debugger as if they were present from the start.
Based on the documentation, I believe autoreload should support this behavior.

Steps to Reproduce

Enable autoreload in the VS Code Python debugger. This is my launch.json in .vscode.

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Moo: Current File",
            "type": "debugpy",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal",
            "autoReload": {
            "enable": true
            }
        }
    ]
}

Start a debugging script in the VS Code editor debugger (via the Run and Debug panel), not the Debug Console with the following sequence:

if __name__=="__main__"
    print('Moo') # Breakpoint here at the start
    print('Baa') # Breakpoint here at the start
    
    #print('Roar') # Uncomment these two lines when at the 'Baa' breakpoint, but before executing 'Baa'
    #print('Woof') # Uncomment these two lines when at the 'Baa' breakpoint, but before executing 'Baa'
    
    print('Quack') # Breakpoint here at the start
    print('Meow') # Breakpoint here at the start
    print('Done') # Breakpoint here at the start

Expected Behavior

The newly added lines should execute as if they were part of the original script when the debugger resumes.

Moo
Baa
Roar
Woof
Quack
Meow
Done

Actual Behavior

The output is

Moo
Baa
Quack
Meow
Done

The two added lines during debugging are ignored.

Environment

VS Code Version: 1.104.3
Python extension for VS Code: 2025.14.0
Python Debugger extension for VS Code:
2025.10.0
Python version: 3.12.10
OS: Windows_NT x64 10.0.26100

Question

Am I using autoreload incorrectly, or is this a bug in the debugger?

Vorherrschende Sprache: TypeScript
Sterne: 181
Forks: 126
Ø Merge: 8 Std. 49 Min.
Gemergte PRs (30 T.): 1

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
Forken Sie das Repository und arbeiten Sie in einem Branch.
Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus microsoft/vscode-python-debugger

Update dependencies with actionable security alerts Offen

triage-needed

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100

microsoft/vscode-python-debugger#1110 · Erstellt am 17.9.2026
PowerShell script debugpy.ps1 incorrectly handles multiple arguments passed as an array Offen

triage-needed

Schwierigkeit 1/5 1-3 Stunden Anfängerfreundlichkeit 88/100

microsoft/vscode-python-debugger#1024 · 1 Kommentar · Erstellt am 07.5.2026
Update dependencies with actionable security alerts Offen

triage-needed

microsoft/vscode-python-debugger#1111 · 1 Reaktion · 1 zugewiesene Person · Erstellt am 17.9.2026
Update vulnerable npm dependencies Offen

triage-needed

microsoft/vscode-python-debugger#1104 · 1 Reaktion · 1 zugewiesene Person · Erstellt am 14.9.2026
Attach process picker still hangs without WMIC because windows-process-tree loader misses node_modules.asar Offen

triage-needed

Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 58/100

microsoft/vscode-python-debugger#1095 · 1 Kommentar · 1 Reaktion · Erstellt am 01.9.2026

Alle Issues in microsoft/vscode-python-debugger