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.
Remove code lenses for "set as interpreter"
See original GitHub issuehttps://github.com/Microsoft/vscode-python/issues/736
I don’t know if you have usage statistics on this but it seems more annoying than useful. I am almost always working within a virtualenv which I set by clicking on the bottom left and selecting my python interpreter.
The hashbang by design is super generic, like #!/usr/bin/env python3. Clicking “set as interpreter” just changes it to system python which is almost always not useful, especially when you’re already in a virtualenv.
I recommend removing this suggestion all together or at the very least removing it when the python path is explicitly listed in settings.json
Issue Analytics
- State:
- Created 5 years ago
- Reactions:21
- Comments:20 (6 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
We are going through old issues and we noticed that no one from the team had replied to this issue. I want to apologize for the oversight and to let you know that the issue was reviewed by the team and triaged (as shown by the labels applied to this issue).
I seem to use CodeLens quite a bit from your link.
I’d advocate for removing it once the python has been explicitly set by user action.