"Run Python File in Terminal" produces "Could not find conda environment"

[stmax82]

Environment data

• VS Code version: 1.38.1
• Extension version: 2019.9.34911
• OS and version: Win 10
• Python version & distribution: Python 3.6, Miniconda
• Type of virtual environment used: conda

Actual behaviour

I have a few python files in c:\temp\foo and I create a local conda environment in c:\temp\foo\myenv with

C:\temp\foo>conda create -p myenv python=3.6

Note that this environment is stored in c:\temp\foo\myenv, not globally.

I can successfully select this environment in VS Code (lower left corner) - it says "Python 3.6.9 64-bit ('myenv': conda)".. fine.

But when I open a python file and select "Python: Run Python File in Terminal" a terminal opens and prints the following error when activating the environment:

C:\temp\foo>activate myenv
Could not find conda environment: myenv
You can list all discoverable environments with `conda info --envs`.


C:\temp\foo>C:/temp/foo/myenv/python.exe c:/temp/foo/test.py
hey

C:\temp\foo>

Expected behaviour

Instead of activate myenv the right thing to run would be activate .\myenv or activate c:\temp\foo\myenv.

[karrtikr]

We are moving to using conda run which runs an executable from within a conda environment without activating it. It won't need activate, so this would be fixing all these issues. Closing this in favor of #7425