New shells activate conda base environment before activating python.pythonPath conda environment

[edwardleardi]

Environment data

• VS Code version: 1.45.1
• Extension version (available under the Extensions sidebar): 2020.5.86806
• OS and version: MacOS Catalina 10.15.5
• Python version (& distribution if applicable, e.g. Anaconda): Anaconda Python 3.6 environment
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
• 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): Jedi
• Value of the python.languageServer setting: Microsoft

Expected behaviour

In my workspace settings I have set:

"python.pythonPath": "/Users/me@home.com/opt/anaconda3/envs/pytorch/bin/python"

So I would expect every time I open a new shell in VS Code the shell runs conda activate pytorch.

Actual behaviour

Each time I open a new shell in the workspace I get this output (before running any commands manually):

source /Users/me@home.com/opt/anaconda3/bin/activate
conda activate pytorch
15:51:44 with me@home.com in pytorch on  master 
❯ source /Users/me@home.com/opt/anaconda3/bin/activate
(base) 15:51:44 with me@home.com in pytorch on  master 
❯ conda activate pytorch
(pytorch) 15:51:44 with me@home.com in pytorch on  master 
❯ 

Is there a reason the shell is running source /Users/me@home.com/opt/anaconda3/bin/activate before activating the pytorch environment? In my ~/.condarc I have auto_activate_base: false so I'm not sure why the base conda environment is being activated at all.

Logs

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

["INFO" - 3:50:41 PM] Extension Name: esbenp.prettier-vscode.
["INFO" - 3:50:41 PM] Extension Version: 5.0.0.
["INFO" - 3:50:41 PM] Enabling prettier for languages
[
  "css",
  "graphql",
  "html",
  "javascript",
  "javascriptreact",
  "json",
  "json5",
  "jsonc",
  "less",
  "markdown",
  "mdx",
  "mongo",
  "postcss",
  "scss",
  "typescript",
  "typescriptreact",
  "vue",
  "yaml"
]
["INFO" - 3:50:41 PM] Enabling prettier for range supported languages
[
  "graphql",
  "javascript",
  "javascriptreact",
  "json",
  "typescript",
  "typescriptreact"
]

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)

XXXX

[karrtikr]

Yes, the extension sends that. It's because we have noticed some conda versions that the activation doesn't work unless base is activated first. Or if user has not configured his shell manually, this step does it for him.
I understand maybe you don't need that, but many of the users do (or atleast did). How is it causing problems for you?

[karrtikr]

Perhaps #8870 might be of interest to you, if so, please upvote the issue.

[edwardleardi]

Ah I see, thanks for the context @karrtikr. It's not necessarily causing me problems, just unexpected behavior to me. I have upvoted the issue you linked.

[lucacerone]

@karrtikr when activating base is needed to make an environment works, it tipycally means one has a broken conda setup in the first place. Regardless of that, "source /bin/activate" has been deprecated by conda (see this post from anaconda's blog) and one should use "conda activate base" instead.

[karrtikr]

it tipycally means one has a broken conda setup

@lucacerone That may very well be true, however, we try our best to support all kinds of scenario. We've received complaints on our side which is why we went with that just to be safe.

[ghost]

Update: I posted much of this comment as a general feature request here. Please upvote that if you would also like to be able to disable the automatic running of these two lines of code in every new terminal in a VS workspace that has Python extension activated.

I just started using VS Code to integrate my R and Python scripts in a single workspace. This "feature" of the Python extension is really annoying...

Okay, I understand why you may have built something that runs
[PATH]/anaconda3/Scripts/activate
and
conda activate base
when opening terminals that are intended to run python code... But after installing the Python extension, every single new terminal tries to run this code, even those that are not intended for use with python.

I do not need/want these commands to run automatically if I simply open an R terminal, a bash terminal, or some other terminal... Yet, in VS workspaces where the VS Code extension has been activated, these commands are sent every single time a new terminal is open.

Why?
How can we disable this?

Thank you!

[ghost]

Perhaps #8870 might be of interest to you, if so, please upvote the issue.

Upvoted.