[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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:
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.
Ok, though I think the src:notebook package should perhaps build python-notebook and python3-notebook packages, as there's probably no point to have ipython in the package name. 


(I'm sure a transition bug to release.debian.org will be needed)?


I don't believe so.


I'll need to read about transitional packages...


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.
Good (though determining which of them are still current might not be that simple). 

Thanks,

Snark on #debian-python
Reply to: