New environments are not discovered until VS Code reloads

[ericsnowcurrently]

This is a broader version of #656, covering all the environment types (not just limited to the project folder.

[DonJayamanne]

E.g.:

• New conda environments
• New Pipenv environments, etc
• New install of Python environment.

[AndreasBackx]

Could it be possible to add a command to the command palette that allows for a refresh of the interpreters? This wouldn't require automatic detection of changes for all of the possible Python environment solutions, but would still allow for us to use them without reloading VS Code.

[albireox]

Any update on this? It seems to me that adding a palette command to refresh the interpreter list (or a command in the interpreter selector itself) should be relatively simple and much appreciated. It's a bit annoying to have to restart all of VSCode just to be able to assign a newly created venv.

[kimadeline]

We changed the way we perform environment discovery, and there is now a refresh button in the top right corner of the environment quickpick: