Conda Activation Timing in Integrated Terminal (python: select interpreter feature)

[m1stborn]

Previously, when I opened the integrated terminal in VS Code, the conda activate env_name command would run before the terminal appeared, ensuring a clean experience. However, after reinstalling VS Code, this behavior has changed.

Now, the conda activate env_name command executes after the terminal is visible, causing the command output to appear in the terminal (as shown in the image below).

This change disrupts the seamless experience and is quite annoying.
How can I configure the integrated terminal to return to the previous behavior, where conda activate env runs before the terminal appears?

[anthonykim1]

Does adding "python.experiments.optOutFrom": ["pythonTerminalEnvVarActivation"] to your settings.json change the behavior?

Also do you have shell integration settings enabled? (there is a generic shell integration setting and also one for Python) I'm wondering what your setting for the generic shell integration setting is.

Lastly, does downgrading extension versions (you may have to go down potentially 3 or more (potentially version lower than .14.0 or below) change this behavior?

Also are you on a windows, mac, or linux?

[m1stborn]

Thank you for the suggestions!

Adding "python.experiments.optOutFrom": ["pythonTerminalEnvVarActivation"] to my settings.json did not resolve the issue.
I do have the shell integration settings enabled(both generic shell and the python one).
I am using Windows and connecting to a remote Ubuntu machine via SSH.
My VS Code version is 1.94.2, and the Python extension version is v2024.17.2024101001. This is already an older version, so perhaps I should try updating to a newer version?

[anthonykim1]

I would try the lastest, and also the older ones too (I would start with 16.0 then go down from there)

One clarifying question here though, when you say:

the conda activate env_name command would run before the terminal appeared, ensuring a clean experience.

When you talk about this clean experience. Do you mean you did not see ANY environment related activation command on your terminal at all?

[m1stborn]

Yes, previously the environment related activation is hidden, when I open the terminal the env is already activated and not showing any command.

[anthonykim1]

I see, in that case you would want to an opt into instead of opt out of terminal env var experiment.