Re: Packaging the Jupyter project suite

Hi Julien, On Fri, Sep 25, 2015 at 07:48:30 +0200, Julien Puydt wrote: > There is also something else to discuss since it used to be only IPython : > how to transition. > > Indeed, the current src:ipython package provides several binary packages: > ipython (shell for Python 2), ipython3 (shell f

Re: Packaging the Jupyter project suite

Hi, Le 25/09/2015 14:00, Julien Cristau a écrit : Hi Julien, On Fri, Sep 25, 2015 at 07:48:30 +0200, Julien Puydt wrote: There is also something else to discuss since it used to be only IPython : how to transition. Indeed, the current src:ipython package provides several binary packages: ipy

Re: Packaging the Jupyter project suite

Hi, Le 18/09/2015 17:49, Julien Puydt a écrit : I would like to package the Jupyter suite of software (ex-IPython). Someone asked on IRC if Jupyter was a fork of IPython : no, it's the same upstream, who broke it (or modularized it if you prefer) into chunks, under the "Jupyter project" umbr

Re: Packaging the Jupyter project suite

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 (ipytho

Re: Packaging the Jupyter project suite

Hi, Le 19/09/2015 07:44, Stuart Prescott a écrit : thanks for looking at Jupyter notebooks for us! No problem. Remember that ipython is already in Debian and already has an active maintainer (Julian Taylor). He might already have started work on jupyter too since he may well feel that it's a

Re: Packaging the Jupyter project suite

Hi, Le vendredi 18 sept. 2015 à 14:52:53 (-0700), Thomas Kluyver a écrit : > On Fri, Sep 18, 2015, at 08:49 AM, Julien Puydt wrote: > > 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 concre

Re: Packaging the Jupyter project suite

On Fri, Sep 18, 2015, at 08:49 AM, Julien Puydt wrote: > 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 ipyke

Packaging the Jupyter project suite

Hi, 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 som