Skip to content

[Enhancement] Allow stepping into external libraries #1232

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

Closed
jamesqo opened this issue Mar 28, 2018 · 5 comments
Closed

[Enhancement] Allow stepping into external libraries #1232

jamesqo opened this issue Mar 28, 2018 · 5 comments
Labels
area-debugging feature-request Request for new features or functionality info-needed Issue requires more information from poster

Comments

@jamesqo
Copy link

jamesqo commented Mar 28, 2018

I'm trying to debug an issue I'm having with an external library. When I try "Step Into" on the line that calls into that library, however, it steps over the call. Would it be possible to add a feature allowing users to actually step into external code?

Thanks.

@brettcannon brettcannon added feature-request Request for new features or functionality area-debugging info-needed Issue requires more information from poster labels Mar 29, 2018
@brettcannon
Copy link
Member

Have you tried with our experimental debugger? We just released 2018.3.0 and it has it bundled with it and I think it should do what you want.

@jamesqo
Copy link
Author

jamesqo commented Apr 1, 2018

@brettcannon How do I use the experimental debugger? I see the python.unitTest.useExperimentalDebugger option but I want to debug my app directly.

@jamesqo
Copy link
Author

jamesqo commented Apr 1, 2018

Found #538 and followed the instructions, VSCode is saying Configured debug type 'pythonExperimental' is not supported.

@DonJayamanne
Copy link

That's not the setting you need to use. Please open your launch.json file and change the type from python to pythonExperimental.
Also please ensure you have updated your extension to the latest version.
Finally please provide the information you failed to fill in when creating the issue.

@brettcannon
Copy link
Member

Closing due to lack of response for more info. If the info is provided in the future we will be happy to re-open this.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 11, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-debugging feature-request Request for new features or functionality info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

3 participants