Provide an option to not change the selected interpreter when it doesn't exist #22523
Labels
area-environments
Features relating to handling interpreter environments
community ask
Feature request that the community expressed interest in
feature-request
Request for new features or functionality
needs PR
Ready to be worked on
As noted by @ambv and @pablogsal in episode 3 of their core.py podcast, it's problematic when you select a Python interpreter that you're actively developing as the interpreter to use. This is because when you rebuild Python it will eventually delete the interpreter. The deletion triggers the extension to immediately look for another interpreter to fill in the gaps. This causes issue for Python core developers when they try to navigate to code and they end up in some installed interpreter's stdlib instead of the one they are actively working on.
Probably some setting that doesn't automatically switch the selected interpreter even if it doesn't exist would solve the issue. That way we can just pick back up when it exists again and just continue on working.
The text was updated successfully, but these errors were encountered: