don't default to recently used when selecting interpreter

[zachvalenta]

Environment data

• VS Code version: 1.41.1
• Extension version (available under the Extensions sidebar): 2020.1.58038
• OS and version: macOS 10.14
• Python version (& distribution if applicable, e.g. Anaconda): 3.7

Expected behaviour

Be able to chose from any environment present at venvPath

Actual behaviour

Can only get recently used interpreters

No option to choose from all interpreters

This becomes a problem if you've just created an environment. I sometimes just have to close VS Code a few times or wait until whatever mechanism VS Code uses to track what directories exist at venvPath updates.

I'm using Poetry for environments but I don't think this issue overlaps w/ #8372 insofar as, once VS Code stops showing 'select interpreter' with the 'recently used' flag, I can then see all my Poetry envs.

[karthiknadig]

The recently used there does not refer to recently used interpreters. The recently used there is just referring to the command that was used.

The interpreter selector should show all interpreters it detects. If it is not detecting some interpreters then that is likely a bug in our detection. @zachvalenta Can you provide details on which paths are not searched or which interpreters are missing?

/cc @luabud We might have to bring this up stream. The recently used text there is not adding to the experience and it is confusing.

[DonJayamanne]

not detecting some interpreters then that is likely a bug in our

This list gets refreshed only when reloading VSCode or virtual environment of created in workspace folder. That's by design.

sometimes just have to close VS Code a few times or wait until whatever mechanism VS Code uses to track what

Reloading once is sufficient, however it can take a while to find all the environments. As we do not know which place a a new env had been created, could have been cons or pipenv, or other. Also we are currently unable to monitor fs changes outside the users workspace.

Creating pipenv, pyenv or new conda end will not be available until vsc is reloaded once.
We have a separate issue for this (to refresh the list, I believe @ericsnowcurrently is the author of that issue).
@karthiknadig @luabud /cc

[zachvalenta]

The recently used there does not refer to recently used interpreters. The recently used there is just referring to the command that was used.

aha! never noticed, makes sense

[zachvalenta]

As we do not know which place a a new env had been created, could have been cons or pipenv, or other.

Doesn't VSC know which place a new env has been created (in part) through venvPath?

[luabud]

I believe the issue Don mentioned on the comment above is #2640. Another one also related is #4862 (and perhaps #7132 as well?).

[karthiknadig]

Closing this, since we don't control the recently used, see this issue on VSCode for more details #89816.