"Run Python File in Terminal" command fails due to using "conda run"

Environment data

Version: 1.41.1 (user setup) Commit: 26076a4de974ead31f97692a0d32f90d735645c0 Date: 2019-12-18T14:58:56.166Z Electron: 6.1.5 Chrome: 76.0.3809.146 Node.js: 12.4.0 V8: 7.6.303.31-electron.0 OS: Windows_NT x64 10.0.18363

I’m using Conda environments, conda version 4.8.0

Expected behaviour

When I invoke the “Run Python File in Terminal” command it should call “python.exe” in the activated environment.

Actual behaviour

The command uses the experimental feature “conda run --name=environment”. This feature doesn’t work yet on my machine. It always invokes the base environment rather than the selected project environment.

Steps to reproduce:

1. create a new anaconda environment with a different python version from base environment
2. select the new environment
3. make sure all terminal sessions are closed
4. run the following file: (resulting in creation of a new terminal window) import sys print(sys.version)

It will print the python version of the base environment.

[Christof23]

@giahung24 if you set "extensions.autoUpdate": false in your settings.json and rollback the python extension to 2019.10.44104 then it fixes the issue.

[paw-lu]

I’m having the same issue on both conda 4.8.0 and 4.8.1.

With script.py as

import sys

print(sys.path)

base ❯ conda run -n env_name python script.py 
['/Users/pcosta/miniconda3/envs/env_name/lib/python37.zip', '/Users/pcosta/miniconda3/envs/env_name/lib/python3.7', '/Users/pcosta/miniconda3/envs/env_name/lib/python3.7/lib-dynload', '/Users/pcosta/miniconda3/envs/env_name/lib/python3.7/site-packages']

base ❯ conda activate env_name

env_name ❯ python script.py
['/Users/pcosta/miniconda3/envs/env_name/lib/python37.zip', '/Users/pcosta/miniconda3/envs/env_name/lib/python3.7', '/Users/pcosta/miniconda3/envs/env_name/lib/python3.7/lib-dynload', '/Users/pcosta/miniconda3/envs/env_name/lib/python3.7/site-packages']

env_name ❯ conda run -n env_name python script.py
['/Users/pcosta/miniconda3/lib/python37.zip', '/Users/pcosta/miniconda3/lib/python3.7', '/Users/pcosta/miniconda3/lib/python3.7/lib-dynload', '/Users/pcosta/miniconda3/lib/python3.7/site-packages']

It seems that running conda run in the activated environment is not running Python in the environment specified.

Since VS Code activates the environment beforehand, then runs conda run when you click the run button, this causes the Python file to run in the wrong environment.