Jupyter doesn't work with anaconda

[zohaad]

Environment data

• VS Code version: 1.33.1
• Extension version (available under the Extensions sidebar): 2019.4.2
• OS and version: macOS Mojave 10.14.3
• Python version (& distribution if applicable, e.g. Anaconda): Python 3.7.1 Anaconda 64-bit
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
• Relevant/affected Python packages and their versions: N/A

Expected behaviour

Jupyter loads correctly

Actual behaviour

it fails to load with anaconda

Steps to reproduce:

1. select code
2. shift + enter

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

Executing code failed : Error: Activating Python 3.7.1 64-bit ('py37': conda) to run Jupyter failed with Error: Command failed: . /anaconda3/envs/py37/bin/activate && conda activate py37 && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python /Users/zohaad/.vscode/extensions/ms-python.python-2019.4.12954/pythonFiles/printEnvVariables.py CommandNotFoundError: 'activate is not a conda command. Did you mean 'source activate'? .

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)

XXX

[rchiodo]

This is not datascience specific. I think the error is we're using '. ' instead of source, although from this
https://github.com/Microsoft/vscode-python/blob/b741e1af6d53cdf94765a6708964d489bd558ff8/src/client/interpreter/activation/service.ts#L105

It looks like it was on purpose.

[aldanor]

@DonJayamanne @rchiodo @xhochy

Building the latest extension version from github master, activation errors still persist with conda.

Basically, before a recent PR (#5516, #4402), I think it was trying to do something like this, which is wrong:

$ <ENV>/activate

Error: activate must be sourced. Run 'source activate envname'
instead of 'activate envname'.

Now it's trying to do something like this (but it's also still wrong!):

$ source <ENV>/bin/activate

Error: no environment provided.

It should be either this:

$ source <ENV>/bin/activate <ENV>

Or, as a matter of fact, conda guys officially suggest using conda activate and conda deactivate instead of sourcing things manually: https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#activating-an-environment

[aldanor]

The only way I can make it work (and this is on conda/macOS) is replacing the <ENV>/activate script in the environment with this one-liner (where <ENV> is the full absolute path to the environment):

export $PATH=<ENV>/bin:$PATH

Then the Jupyter stuff launches fine (just to verify).

[xhochy]

This is weird. The latest nightly is working for me with conda 4.6. What conda version do you have installed?