Python Environments extension doesn't discover venvs in python.venvPath (~/.virtualenvs)

[gpwatsona]

Description

After enabling the Microsoft "Python Environments" extension (it actually enabled itself), my virtualenvwrapper envs in ~/.virtualenvs no longer appear in the VS Code interpreter list. Only Homebrew global Python installs show up.

Disabling the Microsoft extension and re-enabling the deprecated "Python Environment Manager" (donjayamanne) restores discovery of all venvs.

Expected behavior

All envs under python.venvPath should appear in the interpreter dropdown.

Actual behavior

Only global Homebrew interpreters appear. Venvs under ~/.virtualenvs are missing.

Repro steps

1. Set "python.venvPath": "/Users//.virtualenvs"
2. Ensure multiple venvs exist there (virtualenvwrapper style)
3. Enable "Microsoft Python Environments" extension
4. Reload VS Code
5. Open "Python: Select Interpreter"

Workaround

Disable Microsoft Python Environments extension and enable deprecated "Python Environment Manager".

Environment

• OS: macOS
• VS Code: 1.109.5 (Universal)
• Python extension: ms-python.python@2026.2.0
• Python Environments extension: ms-python.vscode-python-envs@1.16.0
• Pylance: ms-python.vscode-pylance@2026.1.1

Settings

"python.venvPath": "/Users//.virtualenvs"

[karthiknadig]

@gpwatsona Please update your envs extension. It should be at 1.20.* for stable and 1.21.* for insiders. I see that you are on 1.16.0.

We now have a global setting at you can set for all type of env searches using:

[karthiknadig]

Please try with Insiders VS Code (version 1.110.0 or greater). This will become available as soon as VS Code releases 1.110.0.
https://code.visualstudio.com/insiders/

[gpwatsona]

Can confirm now working, env version 1.20.1 showed up yesterday and works fine with VSCode 1.109.5

Thanks