after installing Windows updates today, debugging is not working anymore.
This is my active debug configuration:
"launch": {
"version": "0.2.0",
"configurations": [
{
"name": "DEBUG CURR",
"type": "python",
"request": "launch",
"program": "${file}",
"console": "internalConsole",
"justMyCode": false,
"stopOnEntry": false,
}...
When I start the debugger, the menu pops up briefly for 1-2 seconds. But then it closes. There is no output in the console.
It does not stop at set breakpoints.
Does anybody have the same problem? Is there a solution?
System settings
- OS: Microsoft Windows 10 Enterprise (10.0.17763 Build 17763)
- VSCode version 1.64.0
- Python version: 3.8.11 (in the active Anaconda Environment)
Installed VSCode extensions:
- Python (Microsoft) version: v2022.0.1786462952
- Pylance (Microsoft) version: v2022.2.0
-
It seems, the problem is known. But there is no solution... github.com/microsoft/vscode-python/issues/18453 learn.microsoft.com/en-us/answers/questions/724858/…FXG– FXG2022年02月07日 14:37:55 +00:00Commented Feb 7, 2022 at 14:37
-
1Solution found. See my answer...FXG– FXG2022年02月07日 14:57:59 +00:00Commented Feb 7, 2022 at 14:57
-
1I'd say this is rather a workaround, not a solution. In any case, appreciate it.pointysticks45– pointysticks452022年10月06日 11:27:02 +00:00Commented Oct 6, 2022 at 11:27
3 Answers 3
It's an issue with the latest Python Extension for VSCode.
Downgrading the python extension to v2021.12.1559732655 fixes the problem.
5 Comments
2022年8月1日 also works for me. The breaking version seems to be 2022100.2022140 has this bug. Downgrading to 2022年8月1日 works.I've had the same issue with the python plugin v2022.20.2
Going back to 2022年8月1日 resolved it for me as well.
Comments
2022201 also has this issue. Went back to 2022年8月1日 and it works just fine.