Changes between Version 5 and Version 9 of Ticket #25837


Ignore:
Timestamp:
07/20/18 15:18:15 (15 months ago)
Author:
gh-timokau
Comment:

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

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #25837

    • Property Cc arojas gh-timokau infinity0 novoselt pcpa nthiery slelievre saraedum schilly strogdon thansen tmonteil was added
    • Property Keywords sagenb added
  • Ticket #25837 – Description

    v5 v9  
    11An 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.
    22
    3 Reasons to make sagenb optional:
     3== Reasons to make sagenb optional ==
    44
    55- most of its functionalities have been replaced for a while
     
    99- it has various open issues (looking at the "Critical" label in the github repo)
    1010        - unmaintained dependencies (https://github.com/sagemath/sagenb/issues/440#issuecomment-381583952)
    11         - incompatibility with the latest flask-babel (https://github.com/sagemath/sagenb/issues/437)
     11        - --incompatibility with the latest flask-babel (https://github.com/sagemath/sagenb/issues/437)--
    1212        - incompatibility with python3 (https://github.com/sagemath/sagenb/issues/343)
    1313        - an XSS vulnerability, unfixed for 3.5 years (https://github.com/sagemath/sagenb/issues/319)
     
    1717- 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.
    1818
    19 Reasons to keep sagenb around:
     19== Reasons to keep sagenb around ==
    2020
    2121- there are still some features depending on it
     
    2525In 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.
    2626
    27 Tickets and issues tracking progress/going in that direction (issues taken from #22431):
     27== Tickets and issues tracking progress/going in that direction ==
     28
     29=== Necessary to keep all tested behaviour in tact without sagenb ("pass the doctests") ===
     30
     31- port/remove the graph editor
     32
     33- port/remove the graph database navigator
     34
     35- port/remove the interactive debugger
    2836
    2937- #25382: do not include sagenb docs in sage
     38
     39=== Misc changes ===
     40
     41- #25852: add a deprecation warning to the sage notebook
     42
     43- actually make sagenb optional
     44
     45=== Functionality sagenb currently does better than Jupyter ===
    3046
    3147- #25015: object introspection (`<obj>?`) in the Jupyter notebook does not display HTML-formatted docs (esp. with latex formatting), while sagenb does
     
    3551- #9048: `automatic_names` only works in sagenb
    3652
    37 - #25852: add a deprecation warning to the sage notebook
     53- Jupyter's converting to PDF "[comment:8 kind of sucks]"
    3854
    39 - port/remove the graph editor
    40 
    41 - port/remove the graph database navigator
    42 
    43 - port/remove the interactive debugger
    44 
    45 Otherwise relevant:
     55=== Otherwise relevant ===
    4656
    4757- #22431: first step in making sagenb python3 compatible