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

Groups > linux.debian.maint.python > #8930 > unrolled thread

Plan for ipython 5 transition

Back to article view | Back to linux.debian.maint.python

Contents

  Plan for ipython 5 transition Tobias Hansen <thansen@debian.org> - 2016-10-11 03:00 +0200
    RE:Plan for ipython 5 transition PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2016-10-11 08:10 +0200
    Re: Plan for ipython 5 transition Julien Puydt <julien.puydt@laposte.net> - 2016-10-11 08:20 +0200
      Re: Plan for ipython 5 transition Tobias Hansen <thansen@debian.org> - 2016-10-11 09:50 +0200
        Re: Plan for ipython 5 transition Julien Puydt <julien.puydt@laposte.net> - 2016-10-11 14:30 +0200

#8930 — Plan for ipython 5 transition

(Please keep debian-science-sagemath@lists.alioth.debian.org in Cc)

Hi,

so the transition freeze is on November 5 and we would like to get
ipython 5 (and Jupyter) into unstable. It has been in experimental for a
while.

There are two categories of ipython reverse dependencies: The ones that
depend only on ipython and/or ipython3, and the ones that also depend on
packages that do not exist anymore in this form in ipython 5,
ipython(3)-notebook and ipython(3)-qtconsole.

Below is a list of all these reverse dependencies. I just built all the
ones (except one, which I will try later) that have a reverse dependency
only on ipython(3) successfully against ipython 5.1.0-1. Since there
were no problems at all, I hope the packages that have only a simple
dependency on ipython can also be assumed to work with the new version.

I would suggest we should file a transition bug against
release.debian.org very soon, to get the advice of the release team on
how to proceed. Then we should also very soon file bugs against the
packages that depend on ipython(3)-notebook and/or ipython(3)-qtconsole,
so that the maintainers can hopefully help us find solutions. These
packages are:

glueviz, lmfit-py, plotly, sardana, vistrails

Snark, do you want to file the bugs?

Here's the list:

# Build-Depend only on ipython / ipython3:

ipdb             builds with ipython 5.1.0-1
matplotlib       builds with ipython 5.1.0-1
nova             builds with ipython 5.1.0-1
patsy            builds with ipython 5.1.0-1
pysurfer         builds with ipython 5.1.0-1
python-cycler    builds with ipython 5.1.0-1
python-geopandas builds with ipython 5.1.0-1
python-skbio     builds with ipython 5.1.0-1
sfepy            builds with ipython 5.1.0-1
yade             not tried yet (one attempt took too long)


# Build-Depend on ipython(3)-notebook or ipython(3)-qtconsole:

glueviz: ipython (>= 2.3.0)
         ipython3 (>= 2.3.0)
         ipython3-qtconsole (>= 2.3.0)
lmfit-py: ipython-notebook
          ipython3-notebook
plotly: ipython-notebook (>= 2.3.0)
        ipython3-notebook (>= 2.3.0)


# Depend only on ipython / ipython3:

accerciser: accerciser
androguard: androguard
connectomeviewer: connectomeviewer
ipdb: python-ipdb
      python3-ipdb
plaso: plaso
pytango: python-pytango
         python3-pytango
python-pypump: pypump-shell
python-skbio: python-skbio
              python3-skbio
rabbitvcs: rabbitvcs-core
sfepy: python-sfepy
woo: python-woo
     python3-woo
yade: yade


# Depend on ipython(3)-notebook or ipython(3)-qtconsole:

glueviz: glueviz: ipython3
                  ipython3-qtconsole
sardana: python-sardana: ipython
                         ipython-qtconsole
vistrails: vistrails: ipython-qtconsole


Best,
Tobias

[toc] | [next] | [standalone]

#8931

Great, +1 for this long awaited migration :))

here the maintainer of lmfit-py, sardana ans spyder

I will take care of lmfit-py. but I think that the notebook is not a strong constrain for lmfit-py

I did the work for sardana., so it is ok in experimental

I did the work with others for spyder and it is sitting into experimental.

nevertheless this would be antangle with the spyderlib -> spyder migration which need to be done 

guidata, guiqwt and  spykeviewer

in a few days (this week, I will upgrade guidata and guiqwt (job already done and release by the upstream)

for spykeviewer. (I do not have yet filled a bug report).


Cheers


Frederic

[toc] | [prev] | [next] | [standalone]

#8932

Hi,

On 11/10/2016 02:18, Tobias Hansen wrote:

> Snark, do you want to file the bugs?

I'm in the middle of moving -- and I know when I move out, but still 
have no clue where to move in : I'm not as readily available as I would 
like.

I'll give a hand if I can, but I don't think it's a good idea to take 
responsibility just now.

Sorry,

Snark

[toc] | [prev] | [next] | [standalone]

#8933

Hi,

ok, but are you ok with us moving ahead? Is ipython generally ready to
migrate? What about the other related packages (ipykernel,
jupyter_client, jupyter_core, nbconvert, nbformat). Should they all
migrate together? Are they ready (up to questions of transition)?

I did another attempt to build yade against ipython 5 and it failed. So
it needs to be added to the list of reverse depends that need more
attention.

Best,
Tobias

On 10/11/2016 06:53 AM, Julien Puydt wrote:
> Hi,
> 
> On 11/10/2016 02:18, Tobias Hansen wrote:
> 
>> Snark, do you want to file the bugs?
> 
> I'm in the middle of moving -- and I know when I move out, but still
> have no clue where to move in : I'm not as readily available as I would
> like.
> 
> I'll give a hand if I can, but I don't think it's a good idea to take
> responsibility just now.
> 
> Sorry,
> 
> Snark
> 
> _______________________________________________
> Debian-science-sagemath mailing list
> Debian-science-sagemath@lists.alioth.debian.org
> https://lists.alioth.debian.org/mailman/listinfo/debian-science-sagemath

[toc] | [prev] | [next] | [standalone]

#8937

Hi,

On 11/10/2016 09:27, Tobias Hansen wrote:
> ok, but are you ok with us moving ahead? Is ipython generally ready to
> migrate? What about the other related packages (ipykernel,
> jupyter_client, jupyter_core, nbconvert, nbformat). Should they all
> migrate together? Are they ready (up to questions of transition)?

Of course I'm ok with moving ahead!

And yes, everything jupyter-related needs to come together.

Snark

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web