-
-
Notifications
You must be signed in to change notification settings - Fork 317
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
prompt displays two active environments in the vscode terminal #539
Comments
Have you solved it? |
@kingnobro Nope, I'm not even sure what causes this problem |
I also use zsh as my $SHELL. OS:
|
@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
|
@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. |
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
The text was updated successfully, but these errors were encountered: