Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #7304

Re: Packaging the Jupyter project suite

From Julien Puydt <julien.puydt@laposte.net>
Newsgroups linux.debian.maint.python
Subject Re: Packaging the Jupyter project suite
Date 2015-09-21 21:10 +0200
Message-ID <qbeDo-7aE-29@gated-at.bofh.it> (permalink)
References <qa6eT-75X-43@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Hi,

Le 18/09/2015 17:49, Julien Puydt a écrit :
> I would like to package the Jupyter suite of software (ex-IPython).
>
> Of course, that makes quite a few packages to prepare, with a big
> dependency graph. I already sent a few ITP (pickleshare, traitlets), a
> few RFS (path.py), some are in NEW (ipython-genutils)...
>
> What is annoying is that some of the packages have a dependency chain
> going in some way, and an extra dependency chain going the other way.
> For a concrete example, ipykernel depends on ipython... but ipython has
> an extra-dep on ipykernel.
>
> How does one package something like this? Does someone want to lend a hand?

Ok, my current plan is :

(1) wait until path.py out of NEW ;
(2) wait to see testpath and traitlets in NEW (I sent two RFS) ;
(3) pickleshare is waiting for path.py (I shall then RFS, the package is 
ready in the team git repository) ;
(4) that will open the way for an updated ipython (the only "old" package) ;
(5) that will open the way for jupyter-core (I sent an ITP, I have a 
prospective package in a local git repository... it needs ipython) ;
(6) this will open the way to jupyter-client and nbformat (all untouched) ;
(7) this will open the way to ipykernel (untouched) ;
(8) this will open the way to nbconvert, ipyparallel and qtconsole (all 
untouched)
(9) this will open the way to notebook (untouched)
(10) this will open the way to ipywidgets (untouched)

And then, I think Debian will have everything sagemath needs from the 
Jupyter project -- but perhaps others will want more of it.

As you see it is a short ten-steps plan, with some parallelization 
possible in some places.

I'm mostly stuck by IPython for two reasons : (1) it already has a main 
maintainer [it's in the DPMT team umbrella though] and (2) it is in 
subversion, which I don't want to use anymore.

Help would be appreciated (mentoring, sponsoring, packaging... anything!),

Snark on #debian-python

Back to linux.debian.maint.python | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Packaging the Jupyter project suite Julien Puydt <julien.puydt@laposte.net> - 2015-09-18 18:00 +0200
  Re: Packaging the Jupyter project suite Thomas Kluyver <takluyver@fastmail.com> - 2015-09-19 00:10 +0200
    Re: Packaging the Jupyter project suite Julien Puydt <julien.puydt@laposte.net> - 2015-09-19 07:20 +0200
  Re: Packaging the Jupyter project suite Julien Puydt <julien.puydt@laposte.net> - 2015-09-21 21:00 +0200
  Re: Packaging the Jupyter project suite Julien Puydt <julien.puydt@laposte.net> - 2015-09-21 21:10 +0200
  Re: Packaging the Jupyter project suite Julien Puydt <julien.puydt@laposte.net> - 2015-09-25 07:50 +0200
    Re: Packaging the Jupyter project suite Julien Puydt <julien.puydt@laposte.net> - 2015-09-25 14:30 +0200
    Re: Packaging the Jupyter project suite Julien Cristau <julien.cristau@logilab.fr> - 2015-09-25 14:30 +0200

csiph-web