When using venv or global python environment, a new terminal can always start with a conda base instead of performing conda deactivate

[gaoren002]

Descripted as the title, my conda is miniforge.
By the way, directly start with python debugger is ok.

[eleanorjboyd]

Hi! So to clarify the steps you want is to deactivate the conda base before then activating the new conda environment which you selected? Did you run conda init to setup and therefore is conda already initialized in all of your shells?

[gaoren002]

No, I Need to describe more clearly.
When I activate a environment which is not a conda environment, and then I open a vscode terminal manually, I will enter the conda base environment in this terminal, but actually I don't want such a conda environment, which will mix my activated environment with the base conda environment . But the F5 button works right.
I'm using Windows.

[eleanorjboyd]

Would you prefer if "on opening new terminals" no activation was done so you can handle it yourself? You can set "python-envs.terminal.autoActivationType" to "off" to do this

[github-actions]

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.

Happy Coding!