-
Notifications
You must be signed in to change notification settings - Fork 24
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
Discuss options for extension install on a per-user basis or per-conda-environment #10
Comments
I will copy my answer in the chat and expand later:
|
BTW, this is a general discussion so pinging @mmarchetti, @bollwyvl and @malev as well... |
Right. To get a handle on this, try running From that, I'm not seeing a good "share" location in my conda environment, This suggests, without wrapping the On 07:41, Wed, Nov 11, 2015 Damián Avila notifications@github.com wrote:
|
I think we have enough good places... damian-S400CA :: ~ ::
$ jupyter --paths
config:
/home/damian/.jupyter
/home/damian/miniconda3/etc/jupyter
/usr/local/etc/jupyter
/etc/jupyter
data:
/home/damian/.local/share/jupyter
/home/damian/miniconda3/share/jupyter
/usr/local/share/jupyter
/usr/share/jupyter
runtime:
/run/user/1000/jupyter
damian-S400CA :: ~ ::
$ source activate jup
discarding /home/damian/miniconda3/bin from PATH
prepending /home/damian/miniconda3/envs/jup/bin to PATH
(jup)damian-S400CA :: ~ ::
$ jupyter --paths
config:
/home/damian/.jupyter
/home/damian/miniconda3/envs/jup/etc/jupyter
/usr/local/etc/jupyter
/etc/jupyter
data:
/home/damian/.local/share/jupyter
/home/damian/miniconda3/envs/jup/share/jupyter
/usr/local/share/jupyter
/usr/share/jupyter
runtime:
/run/user/1000/jupyter You have Btw, wrapping the notebook makes sense in the future for better handling of several things... and in fact is the methodology already present in wakari that I am migrating to the |
You're right, of course. Was working from memory on phone. The env location I need to look into the config call for enabling but hopefully it's already Really is shaping up that conda is the best way to manage Jupyter The high road would be to actually package the js as npm packages, also On 16:22, Wed, Nov 11, 2015 Damián Avila notifications@github.com wrote:
|
Yep...
I think so, we need to check because I don;t remember...
Yep, there is some issues with multiple users usability of conda... let's see how that evolves in the future...
In fact, I think there is a third agnostic path using build and post script commands... but I agree that eventually a npm based installation based on conda should be one of the path to follow (there is an interesting discussion about how lo load things in the "future" notebookish thing here: https://github.com/phosphorjs/phosphide/issues/1) |
This discussion (and exploration of further options) will continue in a bigger picture here: https://github.com/Anaconda-Server/anaconda-notebook/issues/55. @bollwyvl I can not close this one, can you give me access to this repo? Or close the issue 😉 Thanks! |
On phone, but will add you, too! |
My sense is that we want all extensions to be installed "globally" which will, in fact, mean "in the current conda environment". Ideally we'd like to be able to pass settings through so a user had an option of installing it on a "per user" basis, but then it will be installed outside of conda and will be in all Jupyter instances, which might be problematic.
The text was updated successfully, but these errors were encountered: