On Thu, Aug 16, 2018 at 12:07 AM François Bissey <frp.bis...@gmail.com> wrote: > > > > > On 16/08/2018, at 10:04, John H Palmieri <jhpalmier...@gmail.com> wrote: > > > > On ticket 25382, https://trac.sagemath.org/ticket/25382, the following > > questions have been raised: > > > > - Is the old Sage notebook deprecated? > > > > - If not, should it be? > > > > - In any case, the documentation builds with Python 2. It does not build > > (because sagenb is not Python 3 compatible) with Python 3. Should we > > completely remove the sagenb documentation from the reference manual, or > > should we do it conditionally on whether we're using Python 2 or not? > > > > I'm happy to hear discussion rather than (or in addition to) just votes. > > > > I have just voiced this opinion on the ticket. > Why does sage contains the documentation for sageNB. If it is a separate > package it should provide its own documentation, not a parent package.
There was a time it made sense to do this. SageNB was *the* GUI for Sage, and I think an integral part of the experience of using Sage. For the "average user" it is a much better and more useful work environment than the command-line interface that some of us nerds like (and even then, there are reasons to prefer the notebook). However, there is enough critical mass (not to mention funding) around the Jupyter notebook that it doesn't make as much sense anymore to maintain a parallel and different--and now less familiar--notebook-like UI just for Sage when it's easier to maintain a Sage kernel for Jupyter. However, as discussed in https://trac.sagemath.org/ticket/25837, there are still numerous use cases--especially cases of particular interest for math software--that the SageNB still handles better than Jupyter. So any effort that might be spent on SageNB is probably better spent improving those use cases on Jupyter*. That said, I believe if we remove the SageNB documentation from Sage's main docs (which I support) it should be replaced with some introductory documentation on how to best use Sage in the Jupyter Notebook. Of course, it need not overlap too much with Jupyter's official docs [1]. However, we also have Sage users whose first introduction to Jupyter is through Sage, and (as I sometimes see on ask.sagemath.org) they are not clear about what the relationship is between Sage an Jupyter (sometimes thinking Jupyter *is* Sage or vice versa). So some introductory docs for Sage users on what Jupyter and the Jupyter Notebook are, how Sage integrates with them, and how to most effectively usage Sage with them (e.g. tips like `%display latex`) would seem in order... * Some of these use cases might require improvements to Jupyter itself, though I believe many of them can also be handled through improvements to the Sage Jupyter kernel to take better advantage of some of Jupyter's APIs--especially w.r.t. wrapping different outputs in the appropriate MIME type. [1] https://jupyter-notebook.readthedocs.io/en/stable/notebook.html -- 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.
