conda activate conda-environment not working on windows

[mfittere]

Environment data

• VS Code version: 1.39.2
• Extension version (available under the Extensions sidebar): XXX
• OS and version: Windows 10 Enterprise 1809
• Python version (& distribution if applicable, e.g. Anaconda): conda 4.7.12
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda 4.7.12
• Relevant/affected Python packages and their versions: None
• Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info How to update the language server to the latest stable version #3977): XXX

Expected behaviour

In bash shell:
conda activate PIMSmyApp

-> activates environment PIMSmyApp

This does not work even after running (as advised in the error message)

conda init bash

Actual behaviour

conda activate base

generates the following error message:

CommandNotFoundError: Your shell has not been properly configured to use 'conda activate'.
If using 'conda activate' from a batch script, change your
invocation to 'CALL conda.bat activate'.

To initialize your shell, run

    $ conda init <SHELL_NAME>

Currently supported shells are:
  - bash
  - cmd.exe
  - fish
  - tcsh
  - xonsh
  - zsh
  - powershell

See 'conda init --help' for more information and options.

IMPORTANT: You may need to close and restart your shell after running 'conda init'.

Steps to reproduce:

1. conda activate base

Logs

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

XXX

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

[ericsnowcurrently]

Thanks for letting us know about this, @mfittere. I'll take a look at this today.

[ericsnowcurrently]

It isn't clear from your description how this relates to the Python extension of VS Code. We'd like to try reproducing the problem, but will need more information:

• how are you triggering this problem is VS Code?
• what is in your workspace settings.json file?
• are you only seeing this problem in the VS Code terminal window?

[mfittere]

Hello,

thank you for following this up. I think I might have chosen the wrong channel as it might be a problem with the git bash shell.

• I am triggering this problem by trying to activate any environment, most simply with the base environment:
  conda activate base

• This is the content of my settings.json file:
  { "python.pythonPath": "C:\\Users\\fitterma\\AppData\\Local\\Continuum\\anaconda3", "telemetry.enableCrashReporter": false, "telemetry.enableTelemetry": false, "terminal.integrated.shell.windows": "C:\\Users\\fitterma\\AppData\\Local\\Programs\\Git\\bin\\bash.exe" }

• This problem occurs in the git bash shell and also in VS Code choosing the bash shell. I only noticed it right now. Are you aware of any fix for this?

Many thanks!

[ericsnowcurrently]

@mfittere, I'm not sure how git bash interacts with conda. You are best off either posting something to stack overflow or checking the conda documentation/support.