Extension fails to activate unnamed conda environments #24095
Labels
area-environments
Features relating to handling interpreter environments
bug
Issue identified by VS Code Team member as probable bug
info-needed
Issue requires more information from poster
Description:
Extension is unable to activate unnamed conda environments created using the
conda create -p
command after the latest update. Previously, these environments were activated correctly. No changes were made to the environments themselves, only VS Code and the Python extension were updated. Named conda environments continue to activate without issue.Steps to reproduce:
Expected behavior:
The Python extension should successfully activate the unnamed conda environment and correctly load its packages, as it did before the update.
Actual behavior:
The Python extension fails to activate the environment and displays an error message, indicating "EnvironmentLocationNotFound". The wrong Python interpreter may be selected, leading to issues with code execution and package resolution.
Logs:
Environment:
Additional information:
conda run
command used by the extension. The logs show it's attempting to activate an environment named "env", but the unnamed environment doesn't have a name and is located at "./env", not "/home/USER/miniconda3/envs/env".I have tried restarting VS Code and reinstalling the Python extension, but the issue persists.
Please investigate this issue and provide a fix to restore the ability to activate unnamed conda environments within the Python extension.
The text was updated successfully, but these errors were encountered: