Path: csiph.com!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod
From: Julien Cristau <julien.cristau@logilab.fr>
Newsgroups: linux.debian.maint.python
Subject: Re: Packaging the Jupyter project suite
Date: Fri, 25 Sep 2015 14:30:03 +0200
Message-ID: <qcAiu-1fs-7@gated-at.bofh.it>
References: <qa6eT-75X-43@gated-at.bofh.it> <qcu3o-MY-11@gated-at.bofh.it>
Old-Return-Path: <julien.cristau@logilab.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.23 (2014-03-12)
Approved: robomod@news.nic.it
Lines: 43
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:7314

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 for Python 3),
> ipython-qtconsole (Qt shell for Python 2), ipython3-qtconsole (Qt shell for
> Python 3), ipython-notebook-common (data for the HTML IPython notebook),
> ipython-notebook (HTML IPython notebook for Python 2), ipython3-notebook
> (HTML IPython notebook for Python 3) and ipython-doc (documentation).
> 
> But now, IPython upstream contains (afaik) what used to be in ipython and
> ipython3. There is an upstream qtconsole which should correspond to
> ipython-qtconsole and ipython3-qtconsole. And there is an upstream notebook
> which should correspond to ipython-notebook-common, ipython-notebook and
> ipython3-notebook.
> 
> So, how does one do so users of those packages get the future new ones

The future qtconsole or jupyter-qtconsole source package will likely
have to build transitional ipython-qtconsole and ipython3-qtconsole
packages so user systems get upgraded.  Likewise, the future
jupyter-notebook package should probably build transitional
ipython{,3}-notebook packages.

> (I'm sure a transition bug to release.debian.org will be needed)?

I don't believe so.

> What does one do to the bugs in the current src:ipython package?

The ones that are still relevant can be marked as found in the jupyter
packages as well, or reassigned, I don't think that's an issue.

Cheers,
Julien
-- 
Julien Cristau          <julien.cristau@logilab.fr>
Logilab		        http://www.logilab.fr/
Informatique scientifique & gestion de connaissances