Opened 21 months ago

Last modified 3 months ago

#25837 needs_work task

Make the sage notebook optional — at Initial Version

Reported by: gh-timokau Owned by:
Priority: major Milestone: sage-9.1
Component: packages: standard Keywords: notebook, sagenb
Cc: embray, vbraun, jdemeyer, kcrisman, fbissey, arojas, gh-timokau, infinity0, novoselt, pcpa, nthiery, slelievre, saraedum, schilly, strogdon, thansen, tmonteil, was Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Description

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:

  • most of its functionalities have been replaced for a while
  • it is not actively maintained -- merely on life support (if even that)
  • 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:

  • there are still some features depending on it

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):

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

Otherwise relevant:

  • #22431: first step in making sagenb python3 compatible

Change History (0)

Note: See TracTickets for help on using tickets.