Type: Bug

Behavior

Issue: conda environment not activating correctly
Problem started: 2/7/2025 (After the 2/7 update)
Setting affected: python.terminal.activateEnvironment
Extension version: 2025.0.0
VS Code version: Code 1.97.0 (33fc5a94a3f99ebe7087e8fe79fbe1d37a251016, 2025-02-04T22:41:26.688Z)
OS version: Windows 10 x64 10.0.19045

• When launching a new terminal in PowerShell, the extension incorrectly uses the full path to conda.bat (e.g., D:\Users\username\miniconda3\Library\bin\conda.bat activate my_environment) to activate the environment, instead of the expected conda command (e.g., conda activate my_environment).

• Note that the conda command works fine. The issue is only that the full path is being used in the python.terminal.activateEnvironment automation.

Terminal Log:
(base) PS D:\Users\username\dir> D:\Users\username\miniconda3\Library\bin\conda.BAT activate my_environment
(base) PS D:\Users\username\dir>

Steps to reproduce:

1. Update the Python extension to the latest version as of February 7, 2025.
2. Set the default terminal to PowerShell.
3. Open a new terminal in Visual Studio Code.
4. Observe that the full path to conda.bat is being invoked in place of the conda command in the environment activation process, preventing the environment from being activated correctly.