Skip to content

Make jupyterlab a standard package, update notebook to 7.x #24904

Closed

Description

@slel

This ticket proposes to make JupyterLab a standard package.

This would require converting jupyterlab and jupyterlab_widgets from "pip" packages to "normal" packages (https://doc.sagemath.org/html/en/developer/packaging.html#package-source-types)
and adding their dependencies as "normal" packages as well.
#34450 allows us to use (non-platform) wheels instead of source packages, which simplifies things because we can avoid Javascript dependencies that are only needed at build time.

This is a mechanical task, which is assisted by https://doc.sagemath.org/html/en/developer/packaging.html#utility-script-to-create-packages but not fully automated (dependencies needs to be updated manually).

Discussion/vote:
https://groups.google.com/g/sage-devel/c/orUpb-YXIHk/m/GIxiKN4eDQAJ

Depends on #32069
Depends on #34450
Depends on #34454

CC: @slel @egourgoulhon @antonio-rojas

Component: notebook

Keywords: JupyterLab

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

Activity

  1. added this to the sage-8.2 milestone on Mar 5, 2018
  2. jdemeyer commented on Mar 6, 2018

    @jdemeyer
    Contributor
    comment:1

    There are two "rules" about standard packages:

    1. New standard packages should be optional first.

    2. There should be a discussion/vote on sage-devel for a new standard package.

    Of course, exceptions are always possible for good reasons, but I see no such reason for jupyterlab.

  3. slel commented on Aug 15, 2018

    @slel
    MemberAuthor
    comment:2

    Dependency: #26059 Make JupyterLab an optional package.

  4. slel commented on Aug 15, 2018

    @slel
    MemberAuthor

    Changed keywords from none to JupyterLab

  5. slel commented on Aug 15, 2018

    @slel
    MemberAuthor

    Dependencies: #26059

  6. slel commented on Aug 15, 2018

    @slel
    Author
  7. slel commented on May 20, 2019

    @slel
    MemberAuthor
    comment:3

    Change milestone to sage-wishlist for a few tickets whose previous milestone is closed.

  8. removed this from the sage-8.2 milestone on May 20, 2019
  9. slel commented on May 24, 2019

    @slel
    Author
  10. mkoeppe commented on Aug 28, 2020

    @mkoeppe
    Contributor

    Changed dependencies from #26059 to #30246

  11. mkoeppe commented on Aug 28, 2020

    @mkoeppe
  12. mkoeppe commented on Feb 13, 2021

    @mkoeppe
    Contributor
    comment:7

    Setting new milestone based on a cursory review of ticket status, priority, and last modification date.

  13. mkoeppe commented on Jun 28, 2021

    @mkoeppe
    Contributor

    Changed dependencies from #30246 to #32069

  14. mkoeppe commented on Jun 28, 2021

    @mkoeppe
  15. mkoeppe commented on Mar 22, 2022

    @mkoeppe
  16. mkoeppe commented on Mar 23, 2022

    @mkoeppe
  17. mkoeppe commented on Aug 29, 2022

    @mkoeppe
  18. mkoeppe commented on Aug 29, 2022

    @mkoeppe
    Contributor

    Changed dependencies from #32069 to #32069, #34450

  19. mkoeppe commented on Aug 30, 2022

    @mkoeppe
    Contributor

    Changed dependencies from #32069, #34450 to #32069, #34450, #34454

  20. mkoeppe commented on Sep 29, 2022

    @mkoeppe
    Contributor
  21. added 2 commits that reference this issue on Dec 4, 2023
    e922bd0
    f336f6a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions