-
Notifications
You must be signed in to change notification settings - Fork 209
installing inside a virtualenv drops random data into my home folder #155
Comments
@RonnyPfannschmidt, what is created in the home folder (Source files, bower components, etc.) ? |
Afair the bower components |
If it's the JS parts of the extension, we're calling the Jupyter API for installing extensions to get that put in place: https://github.com/jupyter-incubator/dashboards/blob/master/setup.py#L29 I did just test it in an virtualenv and noticed that it still prefers to write to the user home directory (in a subpath). Even if we stop overriding the install command, that extension method is still going to want to install outside the virtualenv by default, e.g. on Mac:
None of those are the path of my active virtualenv, which is:
Sounds like it needs to be opened as a notebook bug to respect the virtual env. Might be some workaround we can do here in the meantime ... EDIT: Full output of |
Notebook ref: jupyter/notebook#331 |
Work is underway to provide a common way of doing nbextension installs and configuration in notebook 4.2: jupyter/notebook#878. Not clear yet if this is going to allow notebook to discover JS extensions and config beyond In the meantime, we will:
At least this way there's no surprises on pip install. It still requires the user to run a command that will put JS and config in a subdir of the user home because that's what notebook requires today. A side effect of this work will probably be the renaming of the package from the |
Implemented the install vs activate separation across various repos:
EDIT: also |
@parente I found PR #166 to have pretty clear instructions for when it's available through pip (that the pip install doesn't also install it into Jupyter takes a moment to think through and understand). It took a bit longer to test with the pull request itself, but I was able to install without automatically activating the extension, and activate and deactivate the extension properly. |
Thanks for testing @nitind. We'll synchronize a release across all the above real-soon-now. |
seriously, wtf - thats a no go
The text was updated successfully, but these errors were encountered: