Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support customizing Just My Code settings for interactive window
See original GitHub issueFeature: Notebook Editor, Interactive Window, Python Editor cells
Description
It would be great, not to encounter the interactiveshell.py when debugging.
I uncheck Debug just my code so that I can step into the libraries I use. However, interactiveshell.py is a nuisance here which I really dont need to see or work with.
If interactiveshell.py is of any importance, we can add a separate checkmark for it in the settings that lets the user explicitly enable it (i.e. when debugging, the first code that he/she sees is interactiveshell.py!).
In my humble opinion, 99.99% of the times, no one intends on checking on interactiveshell.py when they start debugging their code.
It would be great to have this out of the way.
Thank you all very much in advance
Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@Coderx7 . Thanks for the report. I don’t think that we would special case one item. Instead we should be respecting the general ptvsd debugging rules: https://github.com/microsoft/ptvsd/issues/997 We’ll take a look to see if we are respecting these in cell debugging, not sure if we currently are or not.
This should be fixed with https://github.com/microsoft/debugpy/issues/664