You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As soon as I start the debugger vs code shuts it down. Reinstalled the python extensions, reinstalled vscode 3 times, restarted computer, reinstalled python 3.13, 3.14 and 3.9, tried different launch.json files - Nothing works. I can't debug anything with vscode, but I can with cmd.
I would like to upvote this issue... I down graded the python debugger extension to 2025.10.0 from 2025.14.0. With the revert to the older extension all debugging worked again.
Oh well, yes - Extension downgraded to 2025.10.0 fixes this. No need to work with the old python debug type in the launch.json. The most recent update (today) from the debugger extension is broken.
Hello everyone! Sorry you are facing this problem and I am looking into right now. I was unable to reproduce the issue you are seeing myself so wanted to ask some follow up questions:
To confirm, the behavior everyone is seeing is that once they start debugging VS Code crashes? And debugging through a launch.json config?
Does it crash if you try and "run and debug file" the button in the top right when you open a python file?
What are the versions of your VS Code, python extension, and python environments extension?
When it fails I was getting an Error dialog saying 'Debug Stopped' when I pressed F5 to debug.
I switched from my desktop where it was failing to my laptop and it ran Ok there. The only obvious differences was the Python version, as listed below.
Desktop
1.105.0 2025.10.0 C:\Program Files\Python311\python.EXE Works
1.105.0 2025.14.0 C:\Program Files\Python311\python.EXE Fails
Laptop
1.105.0 2025.14.0 C:\Program Files\Python313\python.EXE Works
closing in favor of #826 as they seem to be the same. Putting out a fix right now and will let you know when it is out so you can confirm your flow works again. Thanks
Hello! I have put out a release with the fix. It was release 5 minutes ago (so 11:39 PDT) and has the version 2025.15.2025101002 but this specific version number may different across machine types. Please give this a try and let me know if it works. Thanks!
Traceback (most recent call last):
File "c:\Program Files\Python311\Lib\runpy.py", line 198, in _run_module_as_main
return _run_code(code, main_globals, None,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "c:\Program Files\Python311\Lib\runpy.py", line 88, in run_code
exec(code, run_globals)
File "c:\Users\dcleland.vscode\extensions\ms-python.debugpy-2025.15.2025101002-win32-x64\bundled\libs\debugpy\launcher/../..\debugpy_main.py", line 71, in
cli.main()
File "c:\Users\dcleland.vscode\extensions\ms-python.debugpy-2025.15.2025101002-win32-x64\bundled\libs\debugpy\launcher/../..\debugpy/..\debugpy\server\cli.py", line 508, in main
run()
File "c:\Users\dcleland.vscode\extensions\ms-python.debugpy-2025.15.2025101002-win32-x64\bundled\libs\debugpy\launcher/../..\debugpy/..\debugpy\server\cli.py", line 358, in run_file
runpy.run_path(target, run_name="main")
File "c:\Users\dcleland.vscode\extensions\ms-python.debugpy-2025.15.2025101002-win32-x64\bundled\libs\debugpy_vendored\pydevd_pydevd_bundle\pydevd_runpy.py", line 310, in run_path
return _run_module_code(code, init_globals, run_name, pkg_name=pkg_name, script_name=fname)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "c:\Users\dcleland.vscode\extensions\ms-python.debugpy-2025.15.2025101002-win32-x64\bundled\libs\debugpy_vendored\pydevd_pydevd_bundle\pydevd_runpy.py", line 125, in _run_module_code
with _TempModule(mod_name) as temp_module, _ModifiedArgv0(fname):
File "c:\Users\dcleland.vscode\extensions\ms-python.debugpy-2025.15.2025101002-win32-x64\bundled\libs\debugpy_vendored\pydevd_pydevd_bundle\pydevd_runpy.py", line 97, in exit
sys.argv[0] = self._saved_value
~~~~~~~~^^^
IndexError: list assignment index out of range
PS E:\work\python\scripts\renamer> `
Can you confirm it works correctly through the terminal (not with vscode)? Seems like sys.argv is getting mutated but I am not sure how that would connect to the path issue. You could also try running "clear cache and reload" as this may help reset your environment after the previous bug
VSCode didn't want to install it - But I was convincing. Got the version 2025.15.2025101002 running and kept my launch.json with debugpy -> Works like a charm.
Activity
Ariggel commentedon Oct 10, 2025
Something is absolutely off. launch.json was:
And it only works now as:
blongbs commentedon Oct 10, 2025
I would like to upvote this issue... I down graded the python debugger extension to 2025.10.0 from 2025.14.0. With the revert to the older extension all debugging worked again.
dcleland commentedon Oct 10, 2025
I just hit this issue as well. Downgrading the python debugger extension to 2025.10.0 fixed this for me as weill.
Ariggel commentedon Oct 10, 2025
Oh well, yes - Extension downgraded to 2025.10.0 fixes this. No need to work with the old python debug type in the launch.json. The most recent update (today) from the debugger extension is broken.
eleanorjboyd commentedon Oct 10, 2025
Hello everyone! Sorry you are facing this problem and I am looking into right now. I was unable to reproduce the issue you are seeing myself so wanted to ask some follow up questions:
dcleland commentedon Oct 10, 2025
When it fails I was getting an Error dialog saying 'Debug Stopped' when I pressed F5 to debug.
I switched from my desktop where it was failing to my laptop and it ran Ok there. The only obvious differences was the Python version, as listed below.
Desktop
1.105.0 2025.10.0 C:\Program Files\Python311\python.EXE Works
1.105.0 2025.14.0 C:\Program Files\Python311\python.EXE Fails
Laptop
1.105.0 2025.14.0 C:\Program Files\Python313\python.EXE Works
eleanorjboyd commentedon Oct 10, 2025
closing in favor of #826 as they seem to be the same. Putting out a fix right now and will let you know when it is out so you can confirm your flow works again. Thanks
eleanorjboyd commentedon Oct 10, 2025
meant to close as duplicate of #826, sorry
Ariggel commentedon Oct 10, 2025
I'll reproduce in estimated 2 to 3 hours. Just tell us when you deployed sth or if u need some more answers :)
eleanorjboyd commentedon Oct 10, 2025
Hello! I have put out a release with the fix. It was release 5 minutes ago (so 11:39 PDT) and has the version
2025.15.2025101002but this specific version number may different across machine types. Please give this a try and let me know if it works. Thanks!dcleland commentedon Oct 10, 2025
I just got that new version and it fixes the problem I had. I can now debug again. Thanks.
dcleland commentedon Oct 10, 2025
I maybe jumped the gun a little on that. I can now debug my Python script but now errors get thrown on exit, as shown below
`PS E:\work\python\scripts\renamer> e:; cd 'e:\work\python\scripts\renamer'; & 'c:\Program Files\Python311\python.exe' 'c:\Users\dcleland.vscode\extensions\ms-python.debugpy-2025.15.2025101002-win32-x64\bundled\libs\debugpy\launcher' '12192' '--' 'E:\work\python\scripts\renamer\renamer.py'
Traceback (most recent call last):
File "c:\Program Files\Python311\Lib\runpy.py", line 198, in _run_module_as_main
return _run_code(code, main_globals, None,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "c:\Program Files\Python311\Lib\runpy.py", line 88, in run_code
exec(code, run_globals)
File "c:\Users\dcleland.vscode\extensions\ms-python.debugpy-2025.15.2025101002-win32-x64\bundled\libs\debugpy\launcher/../..\debugpy_main.py", line 71, in
cli.main()
File "c:\Users\dcleland.vscode\extensions\ms-python.debugpy-2025.15.2025101002-win32-x64\bundled\libs\debugpy\launcher/../..\debugpy/..\debugpy\server\cli.py", line 508, in main
run()
File "c:\Users\dcleland.vscode\extensions\ms-python.debugpy-2025.15.2025101002-win32-x64\bundled\libs\debugpy\launcher/../..\debugpy/..\debugpy\server\cli.py", line 358, in run_file
runpy.run_path(target, run_name="main")
File "c:\Users\dcleland.vscode\extensions\ms-python.debugpy-2025.15.2025101002-win32-x64\bundled\libs\debugpy_vendored\pydevd_pydevd_bundle\pydevd_runpy.py", line 310, in run_path
return _run_module_code(code, init_globals, run_name, pkg_name=pkg_name, script_name=fname)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "c:\Users\dcleland.vscode\extensions\ms-python.debugpy-2025.15.2025101002-win32-x64\bundled\libs\debugpy_vendored\pydevd_pydevd_bundle\pydevd_runpy.py", line 125, in _run_module_code
with _TempModule(mod_name) as temp_module, _ModifiedArgv0(fname):
File "c:\Users\dcleland.vscode\extensions\ms-python.debugpy-2025.15.2025101002-win32-x64\bundled\libs\debugpy_vendored\pydevd_pydevd_bundle\pydevd_runpy.py", line 97, in exit
sys.argv[0] = self._saved_value
~~~~~~~~^^^
IndexError: list assignment index out of range
PS E:\work\python\scripts\renamer> `
eleanorjboyd commentedon Oct 10, 2025
Can you confirm it works correctly through the terminal (not with vscode)? Seems like
sys.argvis getting mutated but I am not sure how that would connect to the path issue. You could also try running "clear cache and reload" as this may help reset your environment after the previous bugAriggel commentedon Oct 10, 2025
Eleanor Boyd (@eleanorjboyd) Did you revoke the .15 version or am I blind? ^^;
eleanorjboyd commentedon Oct 10, 2025
I still see
2025.15.2025101002listed- is it showing any version released within the past 3 hours? I also see it listed on the marketplace site online: https://marketplace.visualstudio.com/items?itemName=ms-python.debugpy&ssr=false#version-historyAriggel commentedon Oct 10, 2025
VSCode didn't want to install it - But I was convincing. Got the version 2025.15.2025101002 running and kept my launch.json with debugpy -> Works like a charm.
eleanorjboyd commentedon Oct 10, 2025
Great! I will release fix as 2025.14.1 shortly which should help as well