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

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

Bug#952952: RM: src:ipykernel-py2 -- RoM for Python 2 removal

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

Contents

  Bug#952952: RM: src:ipykernel-py2 -- RoM for Python 2 removal Julien Puydt <julien.puydt@laposte.net> - 2020-03-02 10:50 +0100
    Bug#952952: RM: src:ipykernel-py2 -- RoM for Python 2 removal Sandro Tosi <morph@debian.org> - 2020-03-02 15:20 +0100
      Re: Bug#952952: RM: src:ipykernel-py2 -- RoM for Python 2 removal Scott Kitterman <debian@kitterman.com> - 2020-03-02 20:30 +0100
      Bug#952952: RM: src:ipykernel-py2 -- RoM for Python 2 removal Gordon Ball <gordon@chronitis.net> - 2020-03-02 20:40 +0100

#12344 — Bug#952952: RM: src:ipykernel-py2 -- RoM for Python 2 removal

Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: debian-python@lists.debian.org

The src:ipykernel-py2 package provides python-ipykernel, which is to be
removed for the Python 2 removal transition.

Notice that for most packages, a single src:foo package provides both
python-foo and python3-foo, so ftpmasters don't need to get involved ;
but in that case we have a src:ipykernel package providing python3-
ipykernel, and this src:ipykernel-py2 providing python-ipykernel, so
more has to be done.

I checked:
jpuydt@phaeris:~$ ssh mirror.ftp-master.debian.org "dak rm -Rn
ipykernel-py2"
Will remove the following packages from unstable:

ipykernel-py2 |   4.10.1-4 | source
python-ipykernel |   4.10.1-4 | all

Maintainer: Debian Python Modules Team <
python-modules-team@lists.alioth.debian.org>

------------------- Reason -------------------

----------------------------------------------

Checking reverse dependencies...
No dependency problem found.


So I think it's ready to go.

Cheers,

J.Puydt

[toc] | [next] | [standalone]

#12345

> The src:ipykernel-py2 package provides python-ipykernel, which is to be
> removed for the Python 2 removal transition.

Cc-ing Gordon explicitly: the last time we spoke, Gordon wanted to
keep the python2 stack of ipython/ikernel/jupyther for people to still
have a py2 infrastructure to run their notebooks. Is this changed? are
we ready to remove them all?

Regards,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

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

#12346

[Multipart message — attachments visible in raw view] — view raw

On Monday, March 2, 2020 9:14:52 AM EST Sandro Tosi wrote:
> > The src:ipykernel-py2 package provides python-ipykernel, which is to be
> > removed for the Python 2 removal transition.
> 
> Cc-ing Gordon explicitly: the last time we spoke, Gordon wanted to
> keep the python2 stack of ipython/ikernel/jupyther for people to still
> have a py2 infrastructure to run their notebooks. Is this changed? are
> we ready to remove them all?
> 
> Regards,

Personally, I think it should go, but I agree that's what Gordon said he 
wanted.  I've tagged the bug moreinfo so it won't be processed by the FTP Team 
while this is being sorted out.

Scott K

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

#12347

On Mon, Mar 02, 2020 at 09:14:52AM -0500, Sandro Tosi wrote:
> > The src:ipykernel-py2 package provides python-ipykernel, which is to be
> > removed for the Python 2 removal transition.
> 
> Cc-ing Gordon explicitly: the last time we spoke, Gordon wanted to
> keep the python2 stack of ipython/ikernel/jupyther for people to still
> have a py2 infrastructure to run their notebooks. Is this changed? are
> we ready to remove them all?

Hi, and thanks for pinging me on this.

I had originally wanted to hang onto ipykernel-py2 on the basis that it
didn't add much to the dependency tree not in any case blocked by
ipython [0] and is _probably_ useful for a certain amount of legacy
analysis code.

However, keeping support for python2 stuff around when it's blocking the
wider py2removal transition is not really a hill I want to die on. Given
that this bug has been filed, and I'm not actually now using the python2
version myself, I'm inclined to just let the RM happen.

Gordon

[0]: ipykernel -> jupyter-client -> jupyter-core -> pyzmq can be dropped
together, I think all other dependencies are blocked on at least
something else.


> 
> Regards,
> -- 
> Sandro "morph" Tosi
> My website: http://sandrotosi.me/
> Me at Debian: http://wiki.debian.org/SandroTosi
> Twitter: https://twitter.com/sandrotosi

[toc] | [prev] | [standalone]

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

csiph-web