activateEnvInCurrentTerminal does not work unless I restart extension?

[traynier]

I'm new to vscode, and have just installed the Python Environments v1.0.0 extension. Not sure if I'm doing something wrong or its broken?

Basically I set it up, and got it working using "python.terminal.activateEnvInCurrentTerminal": true, and all was looking good.

If I close and re-open vscode it doesn't work - I open a terminal and the environment is not activated. However I have found out that if I go to the extensions, disable the "Python Environments" extension, click the "Restart extensions" button that appears, and then enable Python Environments again, then it starts working again and opening a terminal window activates my venv again.

[eleanorjboyd]

Hi! That is an older setting (which I should look into if we still need it or if I can get rid of it) so it is not doing what I think you mean to do. Your goal is to get the environment to activate on opening a new terminal? These steps should help you

1. Add "python.useEnvironmentsExtension": true, to your USER settings (there is a chance this setting will show as "unknown" but it works)
2. Finally do either:
   A. Do nothing which keeps "python-envs.terminal.autoActivationType" to its default value command and the activation command will be run in each terminal on open
   B. Add "python-envs.terminal.autoActivationType": "shellStartup" to your settings (user or workspace) which will inject the activation script into your shell script for a more automatic activation. Shell startup is only supported for zsh, fsh, pwsh, bash, and cmd.

[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!