Conda environments except 'base' not activated on windows 10 in integrated terminal using cmd.exe

[phloose]

Environment data

• VS Code version: 1.36.1 (system setup)
• Extension version: 2019.6.24221
• OS and version: Windows 10 1809
• Python version : python3 (differs depending on used env) Miniconda3
• Type of virtual environment used: conda 4.7.5
• Jedi or Language Server? : Language server
• Integrated terminal: cmd.exe

Expected behaviour

If python interpreter is set to env-xy (bottom left of statusbar) the respective environment should be activated in the integrated terminal when

• opening new terminal with the plus sign
• running a file in terminal (right click -> run python-file in terminal)
• opening a REPL

Actual behaviour

If environment env-xy is selected and one of the actions mentioned in the bulletpoints is run the respective environment is not activated. It just uses the base environment, regardless of settings made in settings.json. Only the python interactive window is run in env-xy. If you switch back from there to base and open a new terminal activate.bat is run. For other environments this does not happen.

A workaround for now is to activate the environment from the anaconda prompt and then launch vscode from the anaconda prompt.

I remember that switching environments worked before, but unfortunatly i cannot say which update (vscode, python-ext or conda) broke this.

Steps to reproduce:

• Create a new environment conda create -n env-xy python=3.7 with anaconda prompt
• Select python interpreter/conda environment 'env-xy' (bottom left of statusbar)
• run one of the three following actions:
  • open new terminal with the plus sign
  • run a python file (right click -> run python-file in terminal)
  • open a REPL

[phloose]

Ok i just found out that i have to explicitly set

"python.condaPath": "C:\\Users\\xibalba01\\Miniconda3\\Library\\bin\\conda.bat"

Then it works as expected. But i remember that setting this path explicitly was not needed before. Also the initial terminal when opening vscode does not automatically get activated in the chosen environment.

Maybe this helps anybody who encountered the same problem for now.

[DonJayamanne]

lso the initial terminal when opening vscode does not automatically get activated in the chosen environment.

Dup of #5330