Terminal can't switch to the conda env which is created by python extension

[HyphyPan]

I created a Conda environment, and after switching the Python environment to this new environment, I found that the terminal is still using the global Python environment, which is inconsistent with the Conda environment I created. After checking the logs, I discovered that there was an error when switching the Conda environment: 'EnvironmentNameNotFound: Could not find conda environment: .conda'.

[karthiknadig]

@HyphyPan Can you share the entire log?

You can try adding this setting to your user settings, and reload VS Code to see if it helps:

    "python.experiments.optOutFrom": ["pythonTerminalEnvVarActivation"]

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

[yorickreum]

We ran into the exact same issue. Activating it via conda activate .\.conda works without any issues. But VS Code by default uses conda activate .conda and this results in a "EnvironmentNameNotFound" with current miniconda 25.5.1 and PowerShell 7.4.11 (as well as PowerShell 5.1.26100). I suggest you update your code to clearly output a prefix and not a name...

[yorickreum]

Still not fixed. Can we reopen this issue, @karthiknadig?

[edgaremy]

Error also encountered on a fedora linux using vscode, the terminal default conda activate .conda fails while typing conda activate ./.conda works fine.

[yorickreum]

This is such a simple and obvious bug that keeps being so annoying ... unbelievable it's still not fixed.