-
Notifications
You must be signed in to change notification settings - Fork 233
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
Problem installing notebook extension in user mode using Homebrew #85
Comments
I never tried the combination of -user and --sys-prefix, you could try this:
However, I strongly recommend never using --user and never using your system Python. It is much saver setting up a virtualenv or using conda/anaconda. Using --user exposes it too all Python environment and installing things in system Python may mess that up. If you only use the system Python and |
Thanks for the suggestion, using
did the trick. This is a Homebrew python, and not a system python, but good advice. Not sure why you recommend avoiding |
Ah, yes, homebrew should be fine. About using |
That sounds like something I wouldn't have run into before (brew+anaconda), but I probably will at some point, so thanks for pointing it out! P.S. - ipyvolume is a blast! I am enjoying learning how to use it. |
I ran into an issue installing the ipyvolume jupyter extension when ipyvolume was installed in user mode using Homebrew on a Mac. Here's how I installed ipyvolume:
The problem is that the jupyer extension configuration file is not found.
Workaround was to install the extension at a system level:
I don't understand the mechanics of the jupyter notebook extension installation process well enough to know how this would be fixed, but I imagine it could possibly be fixed by passing additional directories to the
jupyter nbextension enable
command (since, when ipyvolume is installed to user space, jupyter nbextension is not searching the directory where those packages are installed, namely,~/Library/Python/3.x/lib/python/site-packages/
).Am opening this issue in case others using Homebrew run into this problem.
The text was updated successfully, but these errors were encountered: