Closed eedwards-sk closed 5 years ago
I have the same results using venv and VS Code version 1.25.1 using the Experimental Python debugger. If I create a new default launch.json with the standard debugger file it ignores my break points completely and just runs through the program.
I can confirm this works in the experimental debugger
Please add the setting "debugStdLib": true
in your launch.json
.
Here's the config settings from my launch.json
:
{
"name": "Python Experimental: Current File (Integrated Terminal)",
"type": "pythonExperimental",
"request": "launch",
"program": "${file}",
"console": "integratedTerminal",
"debugStdLib": true
},
Please test with the above settings and let me know how it goes?
Yes, that did work. Though I think there is still something that has changed in my environment because I have a co-worker running on the same version of VS Code, debugging the same program and he does not have that in his launch.json file. With his, whenever he gets to a "Import" statement it opens up that code being import and you can continue stepping into it. With mine, it now works inside the module(thanks to adding the debugStdLib) but as soon as it hits an import I get an error regarding "Unable to open '
I think my current issue is something outside of VS Code as I have the same issue with pdb. so setting that variable in launch.json does resolve this issue.
@Bullenj01 @eedwards-sk It should be fixed, please test the latest development version of the extension. Instructions can be found here https://github.com/Microsoft/vscode-python/blob/master/CONTRIBUTING.md#development-build
Has the fix been released in the latest published version (2018.9.0) yet? I'm guessing not because I'm running into the same error.
This has not been supported yet. See #2087 for the issue tracking the fix for this.
Environment data
Actual behavior
step-into does not step into library code and merely continues
Expected behavior
step-into steps into library code
Steps to reproduce:
pyenv install 3.6.5
pyenv virtualenv -p python3.6 3.6.5 scratch-3.6
test.py
parser.add_argument( 'foo' )
Logs
Output for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)Output from
Console
under theDeveloper Tools
panel (toggle Developer Tools on underHelp
)