New "conda run" method of running python file not working

[paul-morenkov]

In the newest version (2022.2.1924087327), the way the run python file command works has changed. Not sure if this is a problem with the extension, or with conda (I am using miniforge on an M1 MacBook Pro). Running the command appears to properly activate the environment, but clearly does not actually run the file from within the correct environment, since imports start coming up as "not found".

[yherin]

Same issues, fixed with downgrade to the previous version of this extension. Packages were definitely installed in the conda environment, despite the import failed errors.

[paul-morenkov]

Same issues, fixed with downgrade to the previous version of this extension. Packages were definitely installed in the conda environment, despite the import failed errors.

Curious, are you also on an M1 Mac?

[yherin]

No, linux with amd type CPU. I don't really want to replicate the error now I have everything working, so I don't have an exact error message anymore, but your description matches exactly what I experienced.

[jesseginsberg]

I am getting a similar error ever since the update to use the conda run command. I'm on a windows laptop. When I use the "Run Python File" command, what gets run in my terminal is:

conda run -n my_conda_environment --no-capture-output --live-stream python c:/path/to/my/script.py

The command fails with an import error for a package I know I have installed in the "my_conda_environment" python environment.

If I manually activate "my_conda_environment" and then edit the command in the terminal to just the end part :

python c:/path/to/my/script.py

the script runs fine without a package import error.

I'm curious if anyone has some background on why the change to use the conda run command? I'm not familiar with the command and I couldn't find it listed in the conda documentation here: https://docs.conda.io/projects/conda/en/latest/commands.html.

Thanks,

[karrtikr]

Hi everyone, does it help if "python.terminal.activateEnvironment" is set to false?

[karrtikr]

You can also you use the following workaround #18639 (comment) to downgrade to the previous version of the extension which works fine.

[karrtikr]

Closing as dup of #18634

[karrtikr]

Hi all, please try out the following VSIX which has the potential fix: https://github.com/microsoft/vscode-python/suites/5578467772/artifacts/180581906, let me know if it helps! Use Extension: Install from VSIX command to install the VSIX.