Skip to content

Meta-ticket: Use system Jupyter notebook / JupyterLab #30306

@mkoeppe

Description

@mkoeppe

We wish to support all combinations of the following scenarios:

  1. Running notebook installed in SAGE_LOCAL from SPKG
  2. Running notebook installed in the system python, or in some venv unrelated to Sage
  3. Running notebook on a different host (which has no Sage installation), connecting to the Sage Jupyter kernel (using ssh, or https://pypi.org/project/jupyter-kernel-gateway, or ...)

A. Sage-the-distribution
B. Distribution packaging of Sage (Debian, Conda, ...)
C. Pip-installed sagelib (#30036)

The following data items are relevant:

i. The kernelspec
iii. threejs, jsmol, mathjax data
iiiii. Built Sage documentation

The following installation locations are relevant:

a. data installed with sagelib within the Sage venv, such as src/sage/ext_data
b. data installed within SAGE_LOCAL as part of Sage-the-distribution
c. data installed as "resources" associated with the kernelspec, on the host where notebook runs (see jupyter kernelspec list)
d. data installed as Jupyter nbextensions on the host where notebook runs (see jupyter nbextension list)

Tickets for Sage 9.2:

Tickets for Sage 9.3:

Tickets for Sage 9.4:

Completed in Sage 10.x:

Open:

CC: @antonio-rojas @kiwifb @slel @nbruin @paulmasson @egourgoulhon @kwankyu @jcamp0x2a @williamstein @mezzarobba

Component: user interface

Keywords: sd110, sd111

Issue created by migration from https://trac.sagemath.org/ticket/30306

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions