Changes between Version 9 and Version 10 of Ticket #25837


Ignore:
Timestamp:
07/21/18 09:35:44 (18 months ago)
Author:
jdemeyer
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #25837 – Description

    v9 v10  
    33== Reasons to make sagenb optional ==
    44
    5 - most of its functionalities have been replaced for a while
     5- most of its functionality has been replaced for a while by Jupyter
    66
    7 - it is not actively maintained -- merely on life support (if even that)
     7- it is not actively maintained -- merely on life support
    88
    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)
    14 
    15 - just as a bit of history, @vbraun was already implying sagenb deprecation in 2013: https://github.com/sagemath/sagenb/issues/169#issuecomment-20026780
    1614
    1715- 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.