Make the sage notebook optional

Question

Make the sage notebook optional

Closed this issue 6 years ago · 59 comments

If you're coming from the deprecation notice in the notebook

The legacy SageNB notebook has been effectively deprecated for quite some time.
We are now making that official.
But that does not mean that Sage will not have notebook functionality.
In fact, most of the functionality of the sage notebook can already be replaced by using the Juypter Notebook instead.
For an introduction on how to use the new notebook and convert existing notebooks, see the documentation.

There are some features that are not yet ported to the new notebook however.
We will not completely stop supporting the legacy notebook until those issues are resolved.
Those features are listed below. If there is some feature you're missing that is not listed or you want to give general feedback, feel free to leave a comment on this ticket. If you do not have an account yet, you can log in with a GitHub account.

Implementation details

Reasons to make sagenb optional

most of its functionality has been replaced for a while by Jupyter
it is not actively maintained -- merely on life support
it has various open issues (looking at the "Critical" label in the github repo)
- unmaintained dependencies (sagemath/sagenb#440 (comment))
- incompatibility with the latest flask-babel (sagemath/sagenb#437
- incompatibility with python3 (sagemath/sagenb#343)
- an XSS vulnerability, unfixed for 3.5 years (sagemath/sagenb#319)
and for me personally: I don't want to package it. I feel like it causes a disproportionate amount of issues considering its relatively low value in today's Sage.

Reasons to keep sagenb around

there are still some features depending on it
there might still be people using it. An example would be @kiwifb's university: #25382 comment:16

In making it optional, we still make it possible to use it for now. And when it inevitably breaks further, the people relying on it can weigh the effort of keeping it alive themselves against the effort of switching to the new notebook.

Tickets and issues tracking progress/going in that direction

Necessary to keep all tested behaviour intact without sagenb ("pass the doctests")

#30540: port/remove the graph editor
port/remove the graph database navigator
port/remove the interactive debugger
#25382: do not include sagenb docs in sage

Misc changes

#25852: add a deprecation warning to the sage notebook
#25837: actually make sagenb optional

Functionality sagenb currently does better than Jupyter

#25015: object introspection (<obj>?) in the Jupyter notebook does not display HTML-formatted docs (esp. with latex formatting), while sagenb does
#24784: search_doc does not work in the Jupyter notebook
#9048: automatic_names only works in sagenb
Jupyter's converting to PDF "kind of sucks" (see #23330)
#26101: With Jupyter, view(...) currently displays the pdf in an external pdf viewer, launched from the server. An inline view as in sagenb is nicer and would work remotely as well.
Jupyter does not scroll large output (e.g. matrices) well; see this post on Stackoverflow
probably supports matrix input, which does work in Sage cell server but not in Jupyter as of this Sage support discussion

Otherwise relevant

#22431: first step in making sagenb python3 compatible
https://wiki.sagemath.org/IpythonNotebook (which features of the Sage notebook are missing in the jupyter notebook, to be updated)
MathJax fonts -- I don't know if it was possible to change the font in the legacy notebook either, but it's not easy to configure a different font in Jupyter notebook. See e.g.:
- jupyter/notebook#2536
- https://ask.sagemath.org/question/43082/configuring-mathjax-fonts/

CC: @embray @vbraun @jdemeyer @kcrisman @kiwifb @antonio-rojas @timokau @infinity0 @novoselt @pcpa @nthiery @slel @saraedum @haraldschilly @strogdon @tobihan @sagetrac-tmonteil @williamstein

Component: packages: standard

Keywords: notebook, sagenb

Branch/Commit: u/chapoton/25837 @ ec7931a

Reviewer: Dima Pasechnik, John Palmieri

Issue created by migration from https://trac.sagemath.org/ticket/25837

Answer 1 · 2018-07-12T14:13:22.000Z

comment:1

Some issues I'm aware of related to features that are only in sagenb:

#25015 - object introspection (<obj>?) in the Jupyter notebook does not display HTML-formatted docs (esp. with latex formatting), while sagenb does. I believe Odile might be looking into this now. Not a significantly difficult issue but not trivial either.
#24784 - search_doc does not work in the Jupyter notebook
#9048 - automatic_names only works in sagenb. This was also discussed recently on sage-devel: https://groups.google.com/d/msg/sage-devel/RoBZ36i1xo4/e6ZunaKRAwAJ I believe automatic_names() can be reimplemented in such a way that's mostly independent on the front-end, though one would still need front-end specific hooks for it to work. I haven't tried this yet though.

I think at a minimum these issues should be fixed before taking further steps at abandoning the old sagenb.

Answer 2 · 2018-07-12T15:35:37.000Z

comment:2

I would also say that something "official" when one uses sagenb even when directly that says it is deprecated is necessary.

Answer 3 · 2018-07-12T19:41:35.000Z

Description changed:

--- 
+++ 
@@ -28,6 +28,14 @@
 
 - #25382: do not include sagenb docs in sage
 
+* #25015 - object introspection (`<obj>?`) in the Jupyter notebook does not display HTML-formatted docs (esp. with latex formatting), while sagenb does
+
+* #24784 - `search_doc` does not work in the Jupyter notebook
+
+* #9048 - `automatic_names` only works in sagenb
+
+- add a deprecation warning to the sage notebook
+
 - port/remove the graph editor
 
 - port/remove the graph database navigator

Answer 4 · 2018-07-12T19:43:51.000Z

comment:4

I modified the ticket description to incorporate (read: shamelessly copy) your additions.

It would be nice if we could get the deprecation warning into 8.3 so that users will have at least one release to prepare. Thats a very optimistic estimate of course, but getting it in 8.3 would be nice either way.

Answer 5 · 2018-07-12T19:47:42.000Z

Description changed:

--- 
+++ 
@@ -28,13 +28,13 @@
 
 - #25382: do not include sagenb docs in sage
 
-* #25015 - object introspection (`<obj>?`) in the Jupyter notebook does not display HTML-formatted docs (esp. with latex formatting), while sagenb does
+- #25015: object introspection (`<obj>?`) in the Jupyter notebook does not display HTML-formatted docs (esp. with latex formatting), while sagenb does
 
-* #24784 - `search_doc` does not work in the Jupyter notebook
+- #24784: `search_doc` does not work in the Jupyter notebook
 
-* #9048 - `automatic_names` only works in sagenb
+- #9048: `automatic_names` only works in sagenb
 
-- add a deprecation warning to the sage notebook
+- #25852: add a deprecation warning to the sage notebook
 
 - port/remove the graph editor

Answer 6 · 2018-07-12T19:47:42.000Z

comment:5

I have opened #25852 for that. I have only ever actually started the notebook once. Do you have an idea where best to add such a message? Just print it on the command line?

Answer 7 · 2018-07-12T20:57:49.000Z

comment:6

Probably on the notebook itself as well, which would require changes in sagenb.

Answer 8 · 2018-07-13T06:42:36.000Z

comment:7

cc a few people who package Sage in various ways

Answer 9 · 2018-07-13T06:42:36.000Z

Changed keywords from notebook to notebook, sagenb

Answer 10 · 2018-07-18T13:19:34.000Z

comment:8

Another issue that was brought up here: https://ask.sagemath.org/question/43051/file-download-as-latex/

Converting a Jupyter notebook to PDF kind of sucks at the moment for notebooks that contain a lot of math in latex. There are two main cases in the notebook where latex can appear, and both have issues in sage:

If an object output from a code cell has _render_latex_ then the notebook will display the rendered latex with mathjax. However, when converting the notebook to PDF, nbconvert just takes the plain-text representation of the output, not the latex, and puts it in a verbatim block. Not good, especially not for Sage.
If a markdown cell contains equations in latex, nbconvert will render them correctly, but only if you have pandoc installed. This is already a known issue, but since pandoc does not come with Sage and is not a dependency this makes for a sucky user experience for something that should Just Work.

I'm not sure what to do about the first case; it seems like an issue for nbconvert but I haven't explored it too deeply. For the latter case (which probably also affects the first case) I wonder if we shouldn't just make pandoc another sage dependency.

Answer 11 · 2018-07-20T15:18:15.000Z

Description changed:

--- 
+++ 
@@ -1,6 +1,6 @@
 An intention to eventually deprecate sagenb has already been mentioned many times in different tickets. But I couldn't find a ticket tracking progress and discussing sagenb's future, so here it is.
 
-Reasons to make sagenb optional:
+## Reasons to make sagenb optional
 
 - most of its functionalities have been replaced for a while
 
@@ -8,7 +8,7 @@
 
 - it has various open issues (looking at the "Critical" label in the github repo)
  	- unmaintained dependencies (https://github.com/sagemath/sagenb/issues/440#issuecomment-381583952)
- 	- incompatibility with the latest flask-babel (https://github.com/sagemath/sagenb/issues/437)
+ 	- --incompatibility with the latest flask-babel (https://github.com/sagemath/sagenb/issues/437)--
  	- incompatibility with python3 (https://github.com/sagemath/sagenb/issues/343)
  	- an XSS vulnerability, unfixed for 3.5 years (https://github.com/sagemath/sagenb/issues/319)
 
@@ -16,7 +16,7 @@
 
 - and for me personally: I don't want to package it. I feel like it causes an unproportional amount of issues considering its relatively low value in todays sage.
 
-Reasons to keep sagenb around:
+## Reasons to keep sagenb around
 
 - there are still some features depending on it
 
@@ -24,9 +24,25 @@
 
 In making it optional, we still make it possible to use it for now. An when it inevitably breaks further, the people relying on it can weigh the effort of keeping it alive themselves against the effort of switching to the new notebook.
 
-Tickets and issues tracking progress/going in that direction (issues taken from #22431):
+## Tickets and issues tracking progress/going in that direction
+
+### Necessary to keep all tested behaviour in tact without sagenb ("pass the doctests")
+
+- port/remove the graph editor
+
+- port/remove the graph database navigator
+
+- port/remove the interactive debugger
 
 - #25382: do not include sagenb docs in sage
+
+### Misc changes
+
+- #25852: add a deprecation warning to the sage notebook
+
+- actually make sagenb optional
+
+### Functionality sagenb currently does better than Jupyter
 
 - #25015: object introspection (`<obj>?`) in the Jupyter notebook does not display HTML-formatted docs (esp. with latex formatting), while sagenb does
 
@@ -34,14 +50,9 @@
 
 - #9048: `automatic_names` only works in sagenb
 
-- #25852: add a deprecation warning to the sage notebook
+- Jupyter's converting to PDF "[kind of sucks](#comment%3A8)"
 
-- port/remove the graph editor
-
-- port/remove the graph database navigator
-
-- port/remove the interactive debugger
-
-Otherwise relevant:
+### Otherwise relevant
 
 - #22431: first step in making sagenb python3 compatible
+

Answer 12 · 2018-07-20T15:18:15.000Z

comment:9

I've updated the ticket. The flask issue was resolved (thanks @fchapoton!), I added the pdf complaint and improved formatting.

Answer 13 · 2018-07-21T09:35:44.000Z

Description changed:

--- 
+++ 
@@ -2,17 +2,15 @@
 
 ## Reasons to make sagenb optional
 
-- most of its functionalities have been replaced for a while
+- most of its functionality has been replaced for a while by Jupyter
 
-- it is not actively maintained -- merely on life support (if even that)
+- it is not actively maintained -- merely on life support
 
 - it has various open issues (looking at the "Critical" label in the github repo)
  	- unmaintained dependencies (https://github.com/sagemath/sagenb/issues/440#issuecomment-381583952)
- 	- --incompatibility with the latest flask-babel (https://github.com/sagemath/sagenb/issues/437)--
+ 	- incompatibility with the latest flask-babel (https://github.com/sagemath/sagenb/issues/437)--
  	- incompatibility with python3 (https://github.com/sagemath/sagenb/issues/343)
  	- an XSS vulnerability, unfixed for 3.5 years (https://github.com/sagemath/sagenb/issues/319)
-
-- just as a bit of history, @vbraun was already implying sagenb deprecation in 2013: https://github.com/sagemath/sagenb/issues/169#issuecomment-20026780
 
 - and for me personally: I don't want to package it. I feel like it causes an unproportional amount of issues considering its relatively low value in todays sage.

Answer 14 · 2018-07-23T16:06:30.000Z

comment:11

I've added a section intended for end users. Please improve on that if you have more knowledge about sagenb or the Jupyter Notebook, which you probably do.

Answer 15 · 2018-07-23T16:06:30.000Z

Description changed:

--- 
+++ 
@@ -1,4 +1,16 @@
-An intention to eventually deprecate sagenb has already been mentioned many times in different tickets. But I couldn't find a ticket tracking progress and discussing sagenb's future, so here it is.
+# If you're coming from the deprecation notice in the notebook
+
+The legacy sage notebook has been effectively deprecated for quite some time.
+We are now making that official.
+But that **does not mean that sage will not have notebook functionality**.
+In fact, most of the functionality of the sage notebook can already be replaced by using the Juypter Notebook instead.
+For an introduction on how to use the new notebook and convert existing notebooks, see [the documentation](http://jupyter-notebook.readthedocs.io/en/latest/notebook.html).
+
+There are *some* features that are not yet ported to the new notebook hovever.
+**We will not completely stop supporting the legacy notebook until those issues are resolved.**
+Those features are listed below. If there is some feature you're missing that is not listed or you want to give general feedback, feel free to leave a comment on this ticket. If you do not have an account yet, you can log in with a GitHub account.
+
+# Implementation details
 
 ## Reasons to make sagenb optional

Answer 16 · 2018-07-24T14:34:20.000Z

Description changed:

--- 
+++ 
@@ -65,4 +65,5 @@
 ### Otherwise relevant
 
 - #22431: first step in making sagenb python3 compatible
+- https://wiki.sagemath.org/IpythonNotebook (which features of the Sage notebook are missing in the jupyter notebook, to be updated)

Answer 17 · 2018-07-24T16:58:24.000Z

Description changed:

--- 
+++ 
@@ -60,7 +60,7 @@
 
 - #9048: `automatic_names` only works in sagenb
 
-- Jupyter's converting to PDF "[kind of sucks](#comment%3A8)"
+- Jupyter's converting to PDF "[kind of sucks](#comment%3A8)" (see #23330)
 
 ### Otherwise relevant

Answer 18 · 2018-07-25T09:51:49.000Z

Description changed:

--- 
+++ 
@@ -66,4 +66,7 @@
 
 - #22431: first step in making sagenb python3 compatible
 - https://wiki.sagemath.org/IpythonNotebook (which features of the Sage notebook are missing in the jupyter notebook, to be updated)
+- MathJax fonts--I don't know if it was possible to change the font in the legacy notebook either, but it's not easy to configure a different font in Jupyter notebook.  See e.g.:
+  - https://github.com/jupyter/notebook/issues/2536
+  - https://ask.sagemath.org/question/43082/configuring-mathjax-fonts/

Answer 19 · 2018-07-25T12:13:14.000Z

comment:15

Those features are listed below.

Where is the list? I can't find it.

I touched on this on page 26 of a talk I gave yesterday (https://share.cocalc.com/share/6cd832d3-c523-41e3-9e54-c8f2d2e8fa2a/travel/2018/2018-07-icms/talks/cocalc/slides/slides.html#1)

One example is that if you start running:

for i in range(10):
   print(i)
   sys.stdout.flush()
   time.sleep(1)

then close and open your browser (to simulate a network failure, say), you
should not loose output. In Jupyter, you do.

Answer 20 · 2018-07-25T12:57:57.000Z

comment:16

Replying to @williamstein:

Those features are listed below.

Where is the list? I can't find it.

It's in the description of the ticket, but perhaps that still needs more reformatting, because there are a number of thing "below" that sentence that include, but are not limited to, missing features.

Most of it falls under the heading "Functionality sagenb currently does better than Jupyter" though that list is far from complete. There's also a link to a wiki page listing other issues.

Answer 21 · 2018-08-20T12:29:27.000Z

Description changed:

--- 
+++ 
@@ -62,6 +62,8 @@
 
 - Jupyter's converting to PDF "[kind of sucks](#comment%3A8)" (see #23330)
 
+- With Jupyter, `view(...)` currently displays the pdf in an external pdf viewer, launched from the server. An inline view as in sagenb is nicer and would work remotely as well.
+
 ### Otherwise relevant
 
 - #22431: first step in making sagenb python3 compatible

Answer 22 · 2018-08-20T19:26:52.000Z

Description changed:

--- 
+++ 
@@ -62,7 +62,7 @@
 
 - Jupyter's converting to PDF "[kind of sucks](#comment%3A8)" (see #23330)
 
-- With Jupyter, `view(...)` currently displays the pdf in an external pdf viewer, launched from the server. An inline view as in sagenb is nicer and would work remotely as well.
+- #26101: With Jupyter, `view(...)` currently displays the pdf in an external pdf viewer, launched from the server. An inline view as in sagenb is nicer and would work remotely as well.
 
 ### Otherwise relevant

Answer 23 · 2018-08-20T22:10:30.000Z

comment:19

"#24784: search_doc does not work in the Jupyter notebook" is now ready for review.

Answer 24 · 2018-09-05T06:10:39.000Z

comment:20

Could someone (having the required rights) please now merge the 4 top pull requests in sagenb github, including the one related to the present ticket ?

https://github.com/sagemath/sagenb/pulls

Answer 25 · 2018-10-17T15:58:55.000Z

comment:21

Replying to @fchapoton:

Could someone (having the required rights) please now merge the 4 top pull requests in sagenb github, including the one related to the present ticket ?

https://github.com/sagemath/sagenb/pulls

done, I guess. See #26499 for the new release of sagenb.

Answer 26 · 2018-12-13T16:45:26.000Z

Branch: u/chapoton/25837

Answer 27 · 2018-12-13T16:45:26.000Z

New commits:

`ec7931a`	`make sagenb optional`

Answer 28 · 2018-12-13T16:45:26.000Z

Commit: ec7931a

Answer 29 · 2019-03-02T03:46:07.000Z

Description changed:

--- 
+++ 
@@ -64,6 +64,8 @@
 
 - #26101: With Jupyter, `view(...)` currently displays the pdf in an external pdf viewer, launched from the server. An inline view as in sagenb is nicer and would work remotely as well.
 
+- Jupyter does not scroll large output (e.g. matrices) well; see [this post on Stackoverflow](https://stackoverflow.com/questions/54837044/jupyter-sagemath-horizontal-scroll-output?noredirect=1#comment96670361_54837044)
+
 ### Otherwise relevant
 
 - #22431: first step in making sagenb python3 compatible
@@ -71,4 +73,3 @@
 - MathJax fonts--I don't know if it was possible to change the font in the legacy notebook either, but it's not easy to configure a different font in Jupyter notebook.  See e.g.:
   - https://github.com/jupyter/notebook/issues/2536
   - https://ask.sagemath.org/question/43082/configuring-mathjax-fonts/
-

Answer 30 · 2019-03-05T15:36:23.000Z

comment:25

remaining imports in 8.7.b6 :

git grep "import.*sagenb" src/
src/doc/en/developer/sagenb/index.rst:The most important section involves how to update your new sagenb
src/sage/all.py:lazy_import('sagenb.notebook.notebook_object', 'notebook')
src/sage/all.py:lazy_import('sagenb.notebook.notebook_object', 'inotebook')
src/sage/all.py:lazy_import('sagenb.notebook.sage_email', 'email')
src/sage/all.py:lazy_import('sagenb.notebook.interact', 'interact')
src/sage/graphs/graph_editor.py:    import sagenb.notebook.interact
src/sage/interacts/library.py:        import sagenb.notebook.interact

Answer 31 · 2019-04-09T17:42:59.000Z

comment:26

Apparently this question implies that we should add "can't do the table command" in Jupyter. Is that accurate?

Answer 32 · 2019-04-09T19:47:03.000Z

comment:27

It works for me.

Answer 33 · 2019-04-13T11:32:04.000Z

comment:29

Replying to @kcrisman:

Apparently this question implies that we should add "can't do the table command" in Jupyter. Is that accurate?

Now tracked at #27656.

Answer 34 · 2019-04-14T22:27:14.000Z

comment:30

Does anything stop this from going forward?

Answer 35 · 2019-04-14T22:27:14.000Z

Reviewer: Dima Pasechnik

Answer 36 · 2019-04-15T13:12:22.000Z

comment:31

Does anything stop this from going forward?

Well, does Jupyter actually do all this stuff yet or not?

Also, for people who download a new Sage (which many do, as opposed to pulling and upgrading), it's not clear to me what happens when they try to use the notebook export functionality (which should still be the default as of now). How do they acquire this optional package if they have a binary-only Sage? Or would the export still accurately export to Jupyter anyway?

Answer 37 · 2019-04-15T15:03:55.000Z

comment:32

IMO there shouldn't be any rush on this until at a minimum the issues listed in the description of this ticket are dealt with.

Is there a reason to rush this forward? If so, what tickets could use my help?

Answer 38 · 2019-04-27T18:51:31.000Z

Description changed:

--- 
+++ 
@@ -66,6 +66,8 @@
 
 - Jupyter does not scroll large output (e.g. matrices) well; see [this post on Stackoverflow](https://stackoverflow.com/questions/54837044/jupyter-sagemath-horizontal-scroll-output?noredirect=1#comment96670361_54837044)
 
+- probably supports matrix input, which does work in Sage cell server but not in Jupyter as of [this Sage support discussion](https://groups.google.com/d/topic/sage-support/UmTrw7ynt9U/discussion)
+
 ### Otherwise relevant
 
 - #22431: first step in making sagenb python3 compatible

Answer 39 · 2019-06-14T14:50:27.000Z

comment:34

Tickets still needing working or clarification should be moved to the next release milestone at the soonest (please feel free to revert if you think the ticket is close to being resolved).

Answer 40 · 2019-09-16T22:21:24.000Z

comment:35

Replying to @embray:

IMO there shouldn't be any rush on this until at a minimum the issues listed in the description of this ticket are dealt with.

Is there a reason to rush this forward? If so, what tickets could use my help?

If SageNB doesn't work with Python 3, then we will need to drop it when we make the switch. Since the switch is coming up, we should officially deprecate this as soon as possible. If we manage to switch to Python 3 by January 1, we already won't make the required (by Sage policy) 6 months of deprecation time.

Answer 41 · 2019-09-17T07:05:14.000Z

comment:36

SageNB won't be ported to Python 3, it's been clear for ages I think.

I think this patch is potentially breaking the current notebook-launching setup,
as we don't want to have a not always installed package pointed to by
Run the old Sage Notebook menu item.

The latter should not be shown if the package is not installed.
In this case instead a message saying something like "Install sagenb optional package
for the old SageNB" should be there.

Answer 42 · 2019-09-21T10:21:14.000Z

comment:37

Replying to @jhpalmieri:

Replying to @embray:

IMO there shouldn't be any rush on this until at a minimum the issues listed in the description of this ticket are dealt with.

Is there a reason to rush this forward? If so, what tickets could use my help?

If SageNB doesn't work with Python 3, then we will need to drop it when we make the switch. Since the switch is coming up, we should officially deprecate this as soon as possible. If we manage to switch to Python 3 by January 1, we already won't make the required (by Sage policy) 6 months of deprecation time.

I added a deprecation warning close to a year ago: #25852

So I think we're good on that front if we decide to drop it with the first python3 release. Feature parity is a different issue though.

Answer 43 · 2019-09-23T14:55:07.000Z

comment:38

I have made a pull request to change the front page of the exporter.

vbraun/ExportSageNB#16

Answer 44 · 2019-10-07T15:35:43.000Z

comment:39

This pull request have been merged.

Answer 45 · 2019-11-07T13:40:50.000Z

comment:40

We will not completely stop supporting the legacy notebook until those issues are resolved.

Did those issues get resolved, and/or will they soon? automatic_names for instance would be an actual regression. Does Jupyter now support matrix input for interacts? Just wondering, before the switch is actually pulled ...

Answer 46 · 2019-11-07T14:19:03.000Z

comment:41

And was the graph stuff ever removed as is suggested in the description?

Answer 47 · 2019-11-07T16:20:28.000Z

comment:42

When we talk about regressions, I think the context is: we are imagining people converting their notebooks from SageNB to Jupyter and not using SageNB any more (as opposed to: using SageNB for some tasks, Jupyter for others). In that context, it is also worthwhile to ask what features Jupyter has that SageNB doesn't. I don't think we are just losing things by moving from SageNB to Jupyter; aside from Python 3 compatibility, I think we gain some things by moving to Jupyter. So it is a trade-off. At what point does the balance tip to the Jupyter side? Maybe the Python 3 support is enough on its own, in fact.

Answer 48 · 2019-11-08T01:55:45.000Z

comment:43

Maybe the Python 3 support is enough on its own, in fact.

Obviously that is the consensus decision. I'm just quoting this ticket right now when I mention these things, and would hate to have them disappear for all time. But as you said elsewhere, someone has to work on them.

Answer 49 · 2019-11-23T14:34:32.000Z

comment:44

A functionality that Jupyter is currently missing over sagenb is the rich text editor. This may possibly be resolved by:

https://github.com/jupytercalpoly/jupyterlab-richtext-mode

Answer 50 · 2019-11-23T15:18:28.000Z

comment:45

the most pressing issue is inability to normally use jsmol in Jupyter notebooks, needed to export 3d drawings for animations. We are having a lot of complaints about it.
There is something with the jsmol pop-up menu, which gets cut out by the notebook cell, and can't be used (thus making exports impossible)

jupyter/notebook#1872 discussing this has been opened in 2016 (pity that it was not resolved during ODK).

Answer 51 · 2019-11-24T10:12:07.000Z

comment:46

Indeed; too bad this was not brought up. That being said, we still are in good contact with the Jupyter team :-) So if we provide them with a specific and easy to reproduce example (e.g. through a binder link) on the above issue, there are chances that we can make progress. It would be worth testing how things are in jupyterlab too.

Answer 52 · 2019-11-25T17:12:21.000Z

comment:47

By the way, I note that only jsmol can make stereographic plots for 3d viewing, though I don't know how often this capability is used. (People like it when advertising Sage!)

Answer 53 · 2019-11-25T18:15:06.000Z

comment:48

Replying to @kcrisman:

By the way, I note that only jsmol can make stereographic plots for 3d viewing, though I don't know how often this capability is used. (People like it when advertising Sage!)

can't plotly do it? see e.g. https://plot.ly/~empet/13037.embed

Answer 54 · 2019-11-25T20:34:09.000Z

comment:49

By "only jsmol", I meant the only thing included standard in Sage. What is plotly? (Am I so behind that I missed a major new Sage internal plot mechanism? Yikes.)

Answer 55 · 2019-11-25T20:38:17.000Z

comment:50

I read your comments as "the only Python library that can do this sort if plotting"

plotly is Python library, no idea if it can work in Sage.

Answer 56 · 2019-12-30T14:48:17.000Z

comment:51

Ticket retargeted after milestone closed

Answer 57 · 2020-05-04T20:14:58.000Z

comment:52

This was done another ticket merged for 9.1 (see #29320), should be closed.

But #17590 (update sagenb SPKG.txt) needs work for 9.1

Answer 58 · 2020-05-04T21:07:44.000Z

Changed reviewer from Dima Pasechnik to Dima Pasechnik, John Palmieri

Answer 59 · 2020-10-11T22:49:31.000Z

Description changed:

--- 
+++ 
@@ -1,12 +1,12 @@
 # If you're coming from the deprecation notice in the notebook
 
-The legacy sage notebook has been effectively deprecated for quite some time.
+The legacy SageNB notebook has been effectively deprecated for quite some time.
 We are now making that official.
-But that **does not mean that sage will not have notebook functionality**.
+But that **does not mean that Sage will not have notebook functionality**.
 In fact, most of the functionality of the sage notebook can already be replaced by using the Juypter Notebook instead.
-For an introduction on how to use the new notebook and convert existing notebooks, see [the documentation](http://jupyter-notebook.readthedocs.io/en/latest/notebook.html).
+For an introduction on how to use the new notebook and convert existing notebooks, see [the documentation](https://jupyter-notebook.readthedocs.io/en/latest/notebook.html).
 
-There are *some* features that are not yet ported to the new notebook hovever.
+There are *some* features that are not yet ported to the new notebook however.
 **We will not completely stop supporting the legacy notebook until those issues are resolved.**
 Those features are listed below. If there is some feature you're missing that is not listed or you want to give general feedback, feel free to leave a comment on this ticket. If you do not have an account yet, you can log in with a GitHub account.
 
@@ -24,7 +24,7 @@
  	- incompatibility with python3 (https://github.com/sagemath/sagenb/issues/343)
  	- an XSS vulnerability, unfixed for 3.5 years (https://github.com/sagemath/sagenb/issues/319)
 
-- and for me personally: I don't want to package it. I feel like it causes an unproportional amount of issues considering its relatively low value in todays sage.
+- and for me personally: I don't want to package it. I feel like it causes a disproportionate amount of issues considering its relatively low value in today's Sage.
 
 ## Reasons to keep sagenb around
 
@@ -32,13 +32,13 @@
 
 - there might still be people using it. An example would be @kiwifb's university: [#25382 comment:16](https://github.com/sagemath/sage/issues/25382#comment:16)
 
-In making it optional, we still make it possible to use it for now. An when it inevitably breaks further, the people relying on it can weigh the effort of keeping it alive themselves against the effort of switching to the new notebook.
+In making it optional, we still make it possible to use it for now. And when it inevitably breaks further, the people relying on it can weigh the effort of keeping it alive themselves against the effort of switching to the new notebook.
 
 ## Tickets and issues tracking progress/going in that direction
 
-### Necessary to keep all tested behaviour in tact without sagenb ("pass the doctests")
+### Necessary to keep all tested behaviour intact without sagenb ("pass the doctests")
 
-- port/remove the graph editor
+- #30540: port/remove the graph editor
 
 - port/remove the graph database navigator
 
@@ -50,7 +50,7 @@
 
 - #25852: add a deprecation warning to the sage notebook
 
-- actually make sagenb optional
+- #25837: actually make sagenb optional
 
 ### Functionality sagenb currently does better than Jupyter
 
@@ -72,6 +72,6 @@
 
 - #22431: first step in making sagenb python3 compatible
 - https://wiki.sagemath.org/IpythonNotebook (which features of the Sage notebook are missing in the jupyter notebook, to be updated)
-- MathJax fonts--I don't know if it was possible to change the font in the legacy notebook either, but it's not easy to configure a different font in Jupyter notebook.  See e.g.:
+- MathJax fonts -- I don't know if it was possible to change the font in the legacy notebook either, but it's not easy to configure a different font in Jupyter notebook.  See e.g.:
   - https://github.com/jupyter/notebook/issues/2536
   - https://ask.sagemath.org/question/43082/configuring-mathjax-fonts/