Conda activate fails when running a python script

Install miniconda Create an environment with Python 3.7 in it (on windows) Start VS code Switch to this environment Run a python file.

Expected result: File runs

Actual result:

PS D:\Training\SnakePython> conda activate jupyter
conda : The term 'conda' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ conda activate jupyter
+ ~~~~~
    + CategoryInfo          : ObjectNotFound: (conda:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

[brettcannon]

It’s a discoverability problem like anything else in the extension, so there’s no magic solution here if people are going to skip the documentation. As I said, I made this an enhancement proposal to consider adding a notification, but we obviously have to balance that with the fact we have been criticized in the past for too many prompts, how to word the potential prompt, what actions the prompt should provide, etc.

[luabud]

Yeah I agree there’s a lot of discoverability issues to get this working well 😦

But you’re right, just assigning condaPath wouldn’t fix it. Users need to do “conda init” to configure PowerShell for conda. Or just to launch VS Code through the Anaconda Prompt.

I’m closing this quoting Don on issue https://github.com/Microsoft/vscode-python/issues/5541:

When using powershell, please ensure you have configured powershell for use with Conda (https://www.anaconda.com/conda-4-6-release/) The python extension expects the user to have configured powershell for use with conda. The python extension will not work around this, as we’ve had a number of issues in the past and we’ve discussed this with the Conda team as well, and we’re in agreement that users need to configure their shell for use with Conda.