Replies: 1 comment 1 reply
-
I have found the problem, VSCode 1.90 have a sort of bug that cannot allow python module debug! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Environment data
Actual behavior
I'm experiencing difficulties when trying to debug non-user-defined code (e.g., imported libraries or modules) in a Jupyter notebook using Visual Studio Code (VS Code). While the debugger stops at breakpoints, I am unable to inspect the variables effectively. The cursor stops at breakpoints but remains green instead of yellow, indicating that the debugging session is not fully interactive (the same problem happen even if I use a .py script instead of a jupyter notebook file).
The cursor stops at breakpoints but remains green. I am unable to acquire any information about the variables in the non-user-defined code.
Expected behavior
When the debugger stops at a breakpoint, the cursor should turn yellow, and it should be possible to inspect the variables used in the .py file
Steps to reproduce:
Here is my launch.json configuration:
{
"version": "0.2.0",
"{
configurations": [
{
"name": "Debugpy",
"type": "debugpy",
"request": "launch",
"program": "${file}",
"console": "integratedTerminal",
"justMyCode": false
}
]
}
I'm adding some pictures to better show the error. I've added a breakpoint in the package source code (2nd image) and started the debugger. As you can see, the execution stops at the correct position, but the yellow cursor is not stepping into the package code and stays "outside" in my code.
Beta Was this translation helpful? Give feedback.
All reactions