VS Code not selecting environment in .venv/ on open with Environments extension installed

[nnja]

On Mac OS with the Python & Python Environments extensions installed, VS Code is failing to automatically activate a virtual environment in the .venv/ folder of the project when opened via code . in the terminal, or via opening the folder via the UI.

Despite being present in the Select Python Environment List.

.venv is present in the Python-envs: Workspace Search Paths setting.

To reproduce:

➜  projects uv init pyenvtest
Initialized project `pyenvtest` at `/Users/nina/projects/pyenvtest`
➜  projects cd pyenvtest
➜  pyenvtest git:(main) ✗ uv venv
Using CPython 3.14.4 interpreter at: /opt/homebrew/opt/python@3.14/bin/python3.14
Creating virtual environment at: .venv
Activate with: source .venv/bin/activate
➜  pyenvtest git:(main) ✗ code .

Uninstalling the Python Environments extension fixes the issue, and the environment in .venv/ is automatically selected when VS Code opens.

[nnja]

Doing a little more investigation, and I found this setting in my User settings. To my knowledge, I did not manually add it.

"python-envs.defaultEnvManager": "ms-python.python:system",

Possibly related to this issue? #1118 (comment)

[gboeer]

Probably also related to #1449 #1446 #1467 #1463 #1466 #1431 #1363

[nnja]

Gordon Böer (@gboeer) I took a look through these and they don't seem related. I was able to use the environment selection field without issue.

Probably also related to ...

[eleanorjboyd]

Hello! Did removing "python-envs.defaultEnvManager": "ms-python.python:system", fix the problem? Not sure how that got set but removing that should be the fix. If you end up seeing it add this back then this is a problem that I need to track down. Thanks

[nnja]

Hello! Did removing "python-envs.defaultEnvManager": "ms-python.python:system", fix the problem? Not sure how that got set but removing that should be the fix. If you end up seeing it add this back then this is a problem that I need to track down. Thanks

I manually added "python-envs.defaultEnvManager": "ms-python.python:venv" to my user settings just in case the value gets automatically set or overridden again, and now loading the environment in the .venv folder works as expected when opening VS Code.

[uhrb]

Ended up this deleting the extension - looks like the only way to make it work.