-
Notifications
You must be signed in to change notification settings - Fork 18
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
Activating the environment fails if conda not in default path #16
Comments
One could argue that not having conda itself in PATH means that you don't want to have conda envs activated... at least on windows, you can't activate an env without having access to the
AFAIK that's already happening: https://github.com/Cadair/jupyter_environment_kernels/blob/master/environment_kernels/activate_helper.py#L388 |
When I say fail, it did not fail gracefully maybe we should just add a check to see if activate is in the path before we throw the subprocess? Interesting, that it seems to be passing in the env, because even when I added conda to my path (in the session, not in the .zshrc) it still did not work. |
@Cadair Can you add a stacktrace? |
Is this still the case? |
Hi; we are seeing the same kind of problem. When we do:
And then run jupyter lab/notebook:
If we add conda to the default PATH, it is no longer an issue. |
If conda is not in the default path of the shell activating the environment fails. If possible the env vars from the shell that started the notebook need to be passed to the subprocess.
I discovered this as I have a zsh alias that turns on conda.
ping @JanSchulz
The text was updated successfully, but these errors were encountered: