Feature to disable conda activation when new terminals are opened.

[ghost]

Possibly related to this and this.

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, based on this, 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. Screenshots are below from opening a radian terminal for running R code and when I simply open a bash terminal.

Why are these two lines of code sent for every new terminal after Python extension has been activated?
How can we disable this?

Thank you!

[andycraig]

Sounds like this is waiting on an API that allows environment variables to be set without using the command line: #11963 (comment)

[ghost]

Thanks @andycraig . The setting "python.terminal.activateEnvironment": false works well enough for me. User Tyriar in that other thread indicated that "the activation should not be done by sending commands", so I wonder if I'll run into unexpected behavior later by changing my settings...

Until then, I'll close this issue though as I'm happy with the solution thus far.

Thanks again for linking the other thread, @andycraig !