extension doesn't activate python venv in terminal windows.

[snail-coupe]

The extension information says::

✅ Create activated terminals

However on every instance of VSCode I use, having this extension enabled breaks the auto-activation of python virtual environments in terminals that previously worked fine. This is consistent against multiple versions of VSCode, on multple versions of windows, both running locally and via RemotetSSH to various linux hosts, with various versions of python.

Expected behavior

Opening a terminal activates the selected virtual environment in it,

Actual behavior

Nothing happens other than I get annoyed.

[abel1502]

I have the same problem. 1.30.0 is broken, but downgrading to 1.28.0 works again

[jascomp]

Yeah, the startup times were greatly improved. I went from less than 10 seconds to at least 30 seconds. Sweet!

[eleanorjboyd]

🤖 Thanks for reporting this, and for the note that 1.28.0 worked while 1.30.0 did not. Is terminal auto-activation still failing on the latest extension? If so, please include your OS/remote type, shell, python-envs.terminal.autoActivationType and python.terminal.activateEnvironment settings, and Python Environments trace output plus terminal output from opening a new terminal. Those details will help us pinpoint the regression.