Open deven367 opened 6 months ago
Have you solved it?
@kingnobro Nope, I'm not even sure what causes this problem
I meet the same problem.
I also use zsh as my $SHELL. My environment:
OS: macOS Sonoma 14.3
VSCode:
Version: 1.85.2 (Universal)
Commit: 8b3775030ed1a69b13e4f4c628c612102e30a681
Date: 2024-01-18T06:40:32.531Z
Electron: 25.9.7
ElectronBuildId: 26354273
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Darwin arm64 23.3.0
@deven367 @SWHL Re-install VSCode can solve this issue. But it also means you need to install all extensions again.
@kingnobro I tried to reinstall, but it does not sovle this issue.
@kingnobro I agree with @SWHL, reinstalling does not fix the issue.
@kingnobro I opened this issue in vscode python, and the issue is resolved for me,
Please run
conda config --set auto_activate_base False
@deven367 Thanks a lot
This just happened to me today after I installed the jupyter package with mamba (though I'm not convinced it's a problem with Jupyter). I use bash, Mac Sonoma 14.3.1, though I do have a zsh profile set up that I don't use.
@kingnobro I opened this issue in vscode python, and the issue is resolved for me,
Please run
conda config --set auto_activate_base False
Thx. It did work.
But what if I want conda to still automatically start the base environment when I create a new terminal somewhere else?
Solution to issue cannot be found in the documentation.
Issue
When a VSCode workspace has a preferred environment, it tries to activate that environment, however when the terminal is launched, it still shows that the
base
environment is active.Relaunching the shell does not fix the issue. So, I refresh the shell which
exec $SHELL
and then activate my env of choice manually.I use
zsh
as my$SHELL
.Installed packages
Environment info