-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debug python have issue #12531
Comments
I have the same problem too, however things seem to be weird: I have the same version of vscode and python plugin on my physical OS and virtual OS (both windows 10), however, the debugger of python in vscode performs greatly on my physical OS, yet no highlight on virtual OS. And if I change version of vscode to the last one, everything will be fine. |
Installed packages are considered non-user code (same as standard library), and by default the debugger is configured to not debug it - so you can't step into it, breakpoints in it won't work etc. If you want to debug installed packages, you need to set |
It is not the case. |
Seems like my issue is stranger than this one: I didn't see this issue only appears on some packages, however mine appears on any code... |
Original VSCode issue: microsoft/vscode#100805 |
Since it's re-opened in vscode now, I'm going to close this one, so that there's only one open issue to track and comment on. If this turns out to be extension-specific after further investigation, please re-open. |
Environment data
python.languageServer
setting: both jedi and microsoft have issuesExpected behaviour
debug should have current line highlighted and automatically show variable values when hoverover
Actual behaviour
current only has an edit cursor on current line, not highlighted, no variable hove over value display. only happen on some packages(not all)
Steps to reproduce:
2.start a python file outside of package, and reference the code inside that package
3.use vscode/python plugin to debug.
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
; turn on source maps to make any tracebacks be useful by runningEnable source map support for extension debugging
)The text was updated successfully, but these errors were encountered: