On Sat, Dec 19, 2015 at 10:23 AM, kcrisman <kcris...@gmail.com> wrote: > >>> There are some things which don't work yet in Sage on Jupyter, for >>> example interacts. >> >> >> SageNB interacts don't work, but Jupyter interacts do. The syntax is >> slightly different but it would be easy enough to provide a compatibility >> layer. >> >> The switch is now http://trac.sagemath.org/ticket/19740 (needs review) > > > Huh, that is a pretty big change. Is there any obvious/easy way for people > to migrate sws notebooks to Jupyter? (I assume not.) What would the > rationale for switching to Jupyter be? (Since, as I understand it, it's not > that Sage-specific, but maybe that has been radically improved.) Does one > need to use "from sage.all import *" or is Sage a "kernel" for Jupyter now? > I guess I don't see what the advantages would be (though there may be some > significant ones). Does Sage include all the Jupyter kernels right now, > would that be a problem if (say) someone wanted to use the Julia kernel and > we don't ship Julia? > > (I would have thought that switching to the "personal" SMC would be the more > evident new default, though that is a much bigger project and SMC isn't > really a notebook in the usual sense anyway, that's just part of it.)
Though I would love to push for that, it is unfortunately not a viable option right now. The reasons are (1) it's under major development; e.g., I'm *completely* rewriting how realtime synchronization works at a low level literally right now, (2) the SMC dependencies fundamentally include RethinkDB and Node.js, which are both nontrivial dependencies with many potential issues, and (3) there's very, very little testing of installing SMC "in the wild" and having it work. So I strongly endorse what Volker and others have done to make Jupyter notebook with the Sage kernel more usable as a default notebook, even though like you I have some fundamental concerns. For example, to add to your list above, if you start a for loop running -- doing some interesting computation printing to output -- close your notebook and open it an hour later, the results are just *gone*. But for a personal notebook on your own computer, that's really not such an issue, and eventually it will definitely get addressed in Jupyter. - William -- William (http://wstein.org) -- 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.
