Changes between Version 33 and Version 55 of Ticket #25837


Ignore:
Timestamp:
10/11/20 22:49:31 (2 weeks ago)
Author:
slelievre
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #25837

    • Property Status changed from needs_info to closed
    • Property Milestone changed from sage-8.8 to sage-duplicate/invalid/wontfix
    • Property Reviewers changed from Dima Pasechnik to Dima Pasechnik, John Palmieri
    • Property Resolution changed from to duplicate
  • Ticket #25837 – Description

    v33 v55  
    11= If you're coming from the deprecation notice in the notebook =
    22
    3 The legacy sage notebook has been effectively deprecated for quite some time.
     3The legacy SageNB notebook has been effectively deprecated for quite some time.
    44We are now making that official.
    5 But that **does not mean that sage will not have notebook functionality**.
     5But that **does not mean that Sage will not have notebook functionality**.
    66In fact, most of the functionality of the sage notebook can already be replaced by using the Juypter Notebook instead.
    7 For an introduction on how to use the new notebook and convert existing notebooks, see [http://jupyter-notebook.readthedocs.io/en/latest/notebook.html the documentation].
     7For an introduction on how to use the new notebook and convert existing notebooks, see [https://jupyter-notebook.readthedocs.io/en/latest/notebook.html the documentation].
    88
    9 There are *some* features that are not yet ported to the new notebook hovever.
     9There are *some* features that are not yet ported to the new notebook however.
    1010**We will not completely stop supporting the legacy notebook until those issues are resolved.**
    1111Those 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.
     
    2525        - an XSS vulnerability, unfixed for 3.5 years (https://github.com/sagemath/sagenb/issues/319)
    2626
    27 - 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.
     27- 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.
    2828
    2929== Reasons to keep sagenb around ==
     
    3333- there might still be people using it. An example would be @fbissey's university: https://trac.sagemath.org/ticket/25382#comment:16
    3434
    35 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.
     35In 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.
    3636
    3737== Tickets and issues tracking progress/going in that direction ==
    3838
    39 === Necessary to keep all tested behaviour in tact without sagenb ("pass the doctests") ===
     39=== Necessary to keep all tested behaviour intact without sagenb ("pass the doctests") ===
    4040
    41 - port/remove the graph editor
     41- #30540: port/remove the graph editor
    4242
    4343- port/remove the graph database navigator
     
    5151- #25852: add a deprecation warning to the sage notebook
    5252
    53 - actually make sagenb optional
     53- #25837: actually make sagenb optional
    5454
    5555=== Functionality sagenb currently does better than Jupyter ===
     
    7373- #22431: first step in making sagenb python3 compatible
    7474- https://wiki.sagemath.org/IpythonNotebook (which features of the Sage notebook are missing in the jupyter notebook, to be updated)
    75 - 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.:
     75- 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.:
    7676  - https://github.com/jupyter/notebook/issues/2536
    7777  - https://ask.sagemath.org/question/43082/configuring-mathjax-fonts/