On Fri, Dec 18, 2015 at 6:47 AM, Emmanuel Charpentier <emanuel.charpent...@gmail.com> wrote: > A few addenda : > > Pros : > * The python debugger works in the IPython notebook. Damn useful ! > * Some extensions developed for Python worksheets run in Sage worksheets. > > Cons : > * (Currently) no standard way to create a cell in another language, as > allowed by the Sage notebook's magics such as %maxima : in the current > implementation, they create separate instances of interpreters, which do not > return to the worksheet, even when explicitely terminated. Exceptions :
Wow, that's annoying; I didn't realize they had that limit. > - Python (creates a separate subprocess) > - R, if rpy2 is young enough (but the interpreter used in %%R cells is > different of the one used by r.... functions. This MUST be fixed). > * The lack of interacts is a sore point. But I hear there is work on this > front... > > I don't see what you mean when you say that live documentation is missing. > You can access the online help by typing a function name and a question > mark, and a pager will open on the right page. And the "help" menu contains > a load of links to the manuals and tutorials (this should be extended, by > the way...) > The Sage notebook lets you browse the entire 10K-page reference manual, tutorial, etc., of Sage as live, auto-converted worksheets. This is very useful for people learning Sage. You don't have to copy paste from the docs -- you directly play with them. This was a very cool feature Dorian Raymer added to the Sage notebook in maybe 2007 or 2008. There was some work on trying to create something similar at the Berkeley sage days. > And I find that the "cluttering" of the filesystem (i.e. one worksheet, one > file) is much saner that the Sage notebook "solution" (one worksheet, a > $#!+load of anonymous files hidden in an invisble directory). Agreed... (in defense, the current design was something we came up with in 2006, when we were planning to have *everything* stored in a database, which was the sort of standard way to make websites back then...) > > Hoping that my two cents may help, > > -- > Emmanuel Charpentier > > > > Le vendredi 18 décembre 2015 11:35:53 UTC+1, Jeroen Demeyer a écrit : >> >> Should the Jupyter notebook be the default notebook for the next Sage >> 7.0 release? I don't really have an opinion on the matter. >> >> >> Pros: >> >> * Nice tracebacks! >> * The Jupyter notebook is a mature well-maintained project, unlike >> SageNB. It is widely used in the "scientific Python" community. >> * Availability of other Jupyter kernels besides Sage. >> >> >> Cons: >> >> * Less compatible with Sage: Sage interacts don't work, some graphics >> don't work. >> * Certain features of SageNB are missing: live documentation, >> sharing/publishing of worksheets. >> * It clutters the file system with .ipynb files. >> >> >> Don't cares: >> >> * It's just a default choice, both options remain available. > > -- > 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. -- 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.
