You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Ability to pre-filter Python interpreter list #17176
Originally posted by cdce8p July 2, 2021
With the pythonDeprecatePythonPath experiment the only way to change the interpreter is through the Select Interpreter command. Unfortunately this lists all available once (global, user, venv) which can get messy if multiple different Python versions are installed. For example, for one of my projects the list currently contains 17 entries which makes switching between them more complicated than it needs to be. I almost always only care only about the virtual environments, so there is no value for me to still list the system interpreters. I would love it if I could hide them.
Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 5 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.
I'd actually like to override the Python interpreter list in my workspace. Would that also work for you Marc Mueller (@cdce8p) ?
And that'd be quite easy to implement, right?
There could still be a Show more ... option.
In my project we have multiple interpreters within the project space (Python2 and 3). So as these are neither installed globally or on user space I'm not expecting the extension to browse the whole project for interpreters and find them.
I'd rather have it "remember" previously used interpreters even though they could not be found from interpreter search. I mean that's not impossible but "kinda magic" and I figured that I actually don't ever need the system interpreters in that particular project.
The recently changed sorting of the interpreter list is already a huge improvement. It's just that I still have quite a long list with 17 options when I only really use the virtual environments.
My idea would be to hide the global installs (behind a Show more) if at least one venv is detected. I think that should work for most.
Thank you for submitting your feature request and everyone who considered it! Unfortunately this issue did not receive enough votes over the allotted time, and so we are closing the issue.
Activity
brettcannon commentedon Sep 1, 2021
Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 5 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.
ewerybody commentedon Sep 3, 2021
I'd actually like to override the Python interpreter list in my workspace. Would that also work for you Marc Mueller (@cdce8p) ?
And that'd be quite easy to implement, right?
There could still be a Show more ... option.
In my project we have multiple interpreters within the project space (Python2 and 3). So as these are neither installed globally or on user space I'm not expecting the extension to browse the whole project for interpreters and find them.
I'd rather have it "remember" previously used interpreters even though they could not be found from interpreter search. I mean that's not impossible but "kinda magic" and I figured that I actually don't ever need the system interpreters in that particular project.
cdce8p commentedon Sep 3, 2021
The recently changed sorting of the interpreter list is already a huge improvement. It's just that I still have quite a long list with 17 options when I only really use the virtual environments.
My idea would be to hide the global installs (behind a
Show more) if at least one venv is detected. I think that should work for most.brettcannon commentedon Nov 1, 2021
Thank you for submitting your feature request and everyone who considered it! Unfortunately this issue did not receive enough votes over the allotted time, and so we are closing the issue.
cdce8p commentedon Nov 5, 2021
The Jupyter extension just added something like this. Don't know, but maybe it's easy enough to repurpose here and worth considering again?
From the changelog entry: https://code.visualstudio.com/updates/v1_62#_jupyter
