-
Notifications
You must be signed in to change notification settings - Fork 299
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
Issues with new conda env on WSL #11813
Comments
This environment worked after reloading the window though |
What was the sequence of events here?
I.e. did you create the environment while in VS Code
If you run into this, please could you set logging to |
Yes. Here, I
|
conda1 is the selected kernel, I guess that's why it has that stuff, however I'm not sure what the error about conda activate means |
Basically both Python and Jupyter extensions fail to activate the Conda enviornment. I believe this is the same as microsoft/vscode-python#19965 We must have a lot of users running into this and never get stuff working.. & just give up and leave |
@roblourens Was |
4.12.0 |
@DonJayamanne I checked that script is ran using I cannot reproduce it on my Docker or codespace, so I would need your help in filing this as a bug on conda. |
not sure what you need from me. Rob can replicate this. I'd suggest setting up wsl at your end and trying this, ive seen this in the past as well, probably ssh . i think the issue is the fact that the paths aren't setup correctly, because the login she'll scripts do not run, i found that activating the base env fixed this. |
I've installed the latest jupyter and python pre-release in insiders, and tried the same steps that I listed above, and now I see
|
Duplicate of #11855 |
Testing #11755
Log
jupyter-log.log
The text was updated successfully, but these errors were encountered: