Changes between Version 10 and Version 11 of Ticket #25837


Ignore:
Timestamp:
07/23/18 16:06:30 (16 months ago)
Author:
gh-timokau
Comment:

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.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #25837 – Description

    v10 v11  
    1 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.
     1= If you're coming from the deprecation notice in the notebook =
     2
     3The legacy sage notebook has been effectively deprecated for quite some time.
     4We are now making that official.
     5But that **does not mean that sage will not have notebook functionality**.
     6In fact, most of the functionality of the sage notebook can already be replaced by using the Juypter Notebook instead.
     7For 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].
     8
     9There are *some* features that are not yet ported to the new notebook hovever.
     10**We will not completely stop supporting the legacy notebook until those issues are resolved.**
     11Those 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.
     12
     13= Implementation details =
    214
    315== Reasons to make sagenb optional ==