Dear Nils, Le jeudi 31 mai 2018 18:31:31 UTC+2, Nils Bruin a écrit : > > On Thursday, May 31, 2018 at 4:52:04 AM UTC-7, Emmanuel Charpentier wrote: >> >> I'm grabbing the opportunity to recall that , whereas I have installed >> the Sage kernel in my (systemwide) jupyter installation via the suitable >> "jupyter >> kernelspec install ..." invocation), when I try to use it from the >> systemwide jupyter via the "normal" invocation "jupyter notebook", it >> complains of SAGE_ROOT being undefined and does not lauch Sage. OTOH, if I >> invoke "SAGE_ROOT=<whatever> jupyter notebook", all is fine and dandy. >> My $SAGE_ROOT/sage script is symlinked to /usr/local/bin/, which is on >> my $PATH. >> >> Suggestions ? >> > > Yes, that is very close to my usage scenario as well (as an aside: > "jupyter kernelspec install" on the sage kernel involved COPYING all the > sage documentation into the kernelspec directory. In most scenarios > symlinking it is more appropriate (that's how sage installs its kernel in > its own kernel) >
Should I revert to symlinking ? It seems not : > If you are placing your kernel.json outside of the sage installation > anyway, you can edit the relevant "kernel.json" to refer to "sage" rather > than the hard path to $SAGE_LOCAL/bin/sage that is there presently. The > changes we are discussing here would avoid having to make that edit. > So, at least for now, I'd better *copy* kernel.json (to be able to edit) and symlink the rest (incl. documentation). And the patch under discussion should allow for simple "standard" installation. Right ? -- Emmanuel Charpentier -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
