Regression: python extension no longer allows selecting interpreters from ~/.virtualenvs

[virtuald]

I use virtualenvwrapper, and it's useful to be able to select the interpreter from the auto-populated list that includes interpreters in ~/.virtualenvs

The worst part is that upgrading the extension lost track of my prior python interpreter, so I had to go select it manually.

[virtuald]

Ok, the other annoying part about the new extension changes is that I can't fill in the interpreter location manually, I have to browse to it.

[virtuald]

... and that doesn't work because I can't browse to a hidden folder on macOS.

But, I can command-P the path in -- but now when I select my virtualenv, it refuses to let me select it and it defaults to the homebrew python.

[virtuald]

Current workaround: uninstalled python environments extension and rolled back to vscode-python 2025.10.1.

TL;DR: https://xkcd.com/1172/

[eleanorjboyd]

Hi! Sorry you are facing this, two problems raised here: not finding the virtualenvs venvs and no able to enter the path as a string.

For the first problem can you try running Python: Run Python Environment Tool (PET) in Terminal...
from the command palette. It should spit out a ton of logs and if you can search for the environment you want and let me know if it shows up that would be great. Thanks

[eleanorjboyd]

ok can you try entering it as a string again- its weird but I think it should work. So if you paste it in, just click enter and even though there is not a "selection" showing up in the dropdown it should work even though the UX is kinda weird. Lmk if that works but also we will probably need to update this because it confuses me as well when I tried it myself.

[github-actions]

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.

Happy Coding!