Found a reason why VS cannot correctly activate the specified environment when using miniconda

[johnwas]

Below is the information of directly opening the specified environment "st" in vscode. Note that after execution, the environment is still (base)：

(base) PS D:\Develop\project\SentenceTransformers> E:\DevSoft\miniconda3\Library\bin\conda.BAT activate st
(base) PS D:\Develop\project\SentenceTransformers>

However, if conda is executed without a path, it can be activated successfully. Note that after execution, the environment is successfully switched to (st):

(base) PS D:\Develop\project\SentenceTransformers> conda activate st
(st) PS D:\Develop\project\SentenceTransformers>

By default, vscode will start conda with its own full path, which will cause the above problem.

Perhaps the conda startup script has done a lot of hacks. vscode should use the method without a path to execute conda to correctly activate the specified environment.

[irm-codebase]

Experiencing the same issue in Linux Fedora 41.

This is basically the premier way of using conda/mamba nowadays, so it's quite a problem.

[anthonykim1]

Is E:\DevSoft\miniconda3\Library\bin\conda.BAT activate st being sent to your terminal directly?
I assume you have "python.experiments.optOutFrom": ["pythonTerminalEnvVarActivation"] in that case.

Also what is your locator setting to?

[irm-codebase]

@anthonykim1 not the issue creator, but disabling python.experiments did the trick for me.
Hope that helps.

[johnwas]

Is E:\DevSoft\miniconda3\Library\bin\conda.BAT activate st being sent to your terminal directly? I assume you have "python.experiments.optOutFrom": ["pythonTerminalEnvVarActivation"] in that case.

Also what is your locator setting to?

The first command line " E:\DevSoft\miniconda3\Library\bin\conda.BAT activate st" is triggered by vscode after clicking "create python terminal" on the left.

The second command line "conda activate st" is entered manually.

The "locator setting" has not been set yet.

Hope this information is useful.