On Fri, Nov 2, 2018 at 3:19 PM John Cremona <john.crem...@gmail.com> wrote: > > > > On Fri, 2 Nov 2018 at 13:21, Vincent Delecroix <20100.delecr...@gmail.com> > wrote: >> >> >> >> Le 31/10/2018 à 13:50, Samuel Lelievre a écrit : >> > >> > >> > Le mardi 30 octobre 2018 08:06:15 UTC+1, Frédéric Chapoton a écrit : >> >> >> >> Because we do not have a clean command inside sage to launch the jupyter >> >> noteboook. >> >> >> >> For the moment, we should just try to avoid new people start using the >> >> deprecated sagenb. >> >> >> >>> >> > We could tell people to type >> > >> > sage: !sage -n jupyter >> >> sage: !jupyter notebook >> >> is simpler and more direct > > > -- that works for me, but shutting it down is problematical. After logging > out of browser windows I do Ctrl-C in the sage session window and it freezes, > I have to kill the window. Not a big problem but a bit disconcerting.
I think making `notebook()` work properly with Jupyter is still the easiest and most user-friendly (as well as backwards-compatible with older Sages). If someone would open a ticket and assign it to me I can make that work. It might take a little bit of fancy footwork for it to work well. For example, I think it might help if notebook() returned an object that allowed interaction with the notebook process (e.g. stopping/restarting it; checking its logs). -- 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.
