-
-
Notifications
You must be signed in to change notification settings - Fork 364
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
Conflict with rye python shims #850
Comments
This looks like the same error message as in #847, although that issue mentions Windows 10 and doesn't mention Rye. |
Out of curiosity, if you're not using Rye, do you see the same "Jupyter server process terminated before the initialization completed" error? If so, this might effectively be a duplicate of #847. |
When this happens I can grab the launch script from the log - something like /tmp/jlab_desktopfiS6Bd/launch.sh - and that script starts jupyterlab correctly when I run it separately. So that's mysterious. From the log:
|
I can see now later that the |
It looks like there's an issue concerning using Rye shims with JupyterLab, among other projects: astral-sh/rye#1093 I'll keep this issue open to track it from Jupyter's perspective, but there might need to be some work done in Rye to prevent errors like this one. |
I'll abandon this bug as uv has taken over all rye's features, and I do not use rye anymore. |
Description
In some Rye-using setups:
The error there is "Jupyter server process terminated before the initialization completed"
Reproduce
Expected behavior
jlab notebookfile.ipynb should maybe use the same selected virtual environment "V" that the user interface otherwise defaulted to.
jlab should not try to launch ~/.rye/bin/python as if it is a virtual environment, because it's not (it's a shim for a system interpreter).
Context
The following appeared in the debug log, and this obviously fails, because that activate script does not exist:
This is quite suspicious - the "system python path" is "$HOME/.rye/bin/python" and jlab is treating that as if it's a .venv (it's not, that shim will reexecute to /usr/bin/python which is python 3.10)
Troubleshoot Output
Browser Output (required for interface issues after loading)
Logs (required for issues with loading, server and startup)
Suggested Workaround
Make sure jupyter is not installed in any system interpreter's user site.
Thanks for the nice work on jupyterlab desktop :)
The text was updated successfully, but these errors were encountered: