n-riesco / ijavascript

IJavascript is a javascript kernel for the Jupyter notebook
Other
2.19k stars 185 forks source link

Need ability to install kernel spec globally. #38

Closed bigzachattack closed 9 years ago

bigzachattack commented 9 years ago

Currently --ijs-install-kernel will always install into the user's IPython/Jupyter profile.

IPython/Jupyter also supports global install path of /usr/local/share/jupyter/kernels. By default IPython install-self installs globally and when into the user's profile when the --user option is added.

It would be nice for IJavascript to mirror this behavior.

n-riesco commented 9 years ago

Just a few quick thoughts:

Would a flag like --ijs-install-global-kernel be enough for your needs?

bigzachattack commented 9 years ago

That makes sense.

--ijs-install-global-kernel works just as well. On Jul 23, 2015 4:34 PM, "Nicolas Riesco" notifications@github.com wrote:

Just a few quick thoughts:

  • I'd like to stay backwards-compatible and keep the behaviour of --ijs-install-kernel
  • currently, ijs only parses command flags starting with --ijs-, any other command flags and arguments are passed onto ipython
  • it would be possible to make ijs smarter and parse commands like ijs install-self --user, but I don't think the effort would be justified when adding another flag like --ijs-install-global-kernel would do the job.

Would a flag like --ijs-install-global-kernel be enough for your needs?

— Reply to this email directly or view it on GitHub https://github.com/n-riesco/ijavascript/issues/38#issuecomment-124232586 .

rgbkrk commented 9 years ago

There is a jupyter-paths node package for resolving these paths as well by the way.

n-riesco commented 9 years ago

@rgbkrk Is there anything like that for IPython? I need a cross-platform way to determine the global location of the kernel specs that works with IPython.

rgbkrk commented 9 years ago

I think we could add the pathing support for detecting it on old installations as well. I did this a bit ago and kind of hated straddling all-in-one, hoping to make an ipython-paths package and then just using both to detect which to use.