-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Bugs (UI and feature access) from incorrectly set config paths (macOS homebrew?) #14890
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
Ping? This and other related issues/PRs (jupyter/notebook#6974, jupyter/notebook#7006) seem stalled. I am very happy to help, but would be need some guidance (lots of python experience, but zero experience with jupyter internals). |
Yet more information (but still no solutions) at jupyter/notebook#6974 (comment). TL;DR: the "schemas" issue is due to a call with the incorrect
|
FWIW, and as expected, all of these errors and misbehaviours vanish for the python.org framework build (of 3.12, but I assume more generally), without requiring any special environment variables or other changes. This still lets me install packages by pip and not be wedded to using a venv, so I think I am moving back to this infrastructure from homebrew, at least for now. |
Hi @defjaf Homebrew default python3 is now python@3.12. I tried using venv as recommended on the homebrew formula page. The config paths are still problematic. Using separate virtual environments for x86_64 (Rosetta 2) and for arm64 and rebuilding JupyterLab as well as ipykernel in the appropriate environment works for I am considering moving to Python.org framework. For moving to python.org framework build from homebrew, what specific changes did you have to go through? Thanks in advance. |
Description
On homebrew python installations on macOS, with
pip
installation of packages:There are also related bugs specific to:
Basically, with homebrew python,
jupyter --paths
should have:/opt/homebrew/etc/jupyter
in "config" and/opt/homebrew/share/jupyter
in "data"This can be done by hand with
JUPYTER_PATH=/opt/homebrew/share/jupyter JUPYTER_CONFIG_PATH=/opt/homebrew/etc/jupyter
.(or homebrew should somehow populate the default directories with the contents that it places in those locations).
Note also that the config homebrew directories that does appear in
jupyter --paths
—/opt/homebrew/opt/python@3.11/Frameworks/Python.framework/Versions/3.11/etc/jupyter
— does not exist. The data dir.../share/jupyter
exists (perhaps only afterjupyter build
?) but is different from/opt/homebrew/share/jupyter
.(I don't know if this is unique to macOS — there is also linux homebrew — or indeed if this could be a broader issue, but I've only seen it for this one case.)
Reproduce
In the "base" homebrew python environment (i.e., no venv, and also not the system python), with
jupyter lab
:The problem disappears with
JUPYTER_PATH=/opt/homebrew/share/jupyter JUPYTER_CONFIG_PATH=/opt/homebrew/etc/jupyter
.Expected behavior
When run with those variables set, or in a venv, these issues go away. In particular:
Context
`jupyter --paths`
The text was updated successfully, but these errors were encountered: