Groups > linux.debian.maint.python > #10033

Re: Python 2 removal strategy

Path	csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From	Matthias Klose <doko@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Re: Python 2 removal strategy
Date	Wed, 10 Jan 2018 22:10:02 +0100
Message-ID	<v6vNg-7Lc-1@gated-at.bofh.it> (permalink)
References	<v6rqj-4sq-23@gated-at.bofh.it>
X-Original-To	Ole Streicher <olebole@debian.org>, debian-python@lists.debian.org
X-Mailbox-Line	From debian-python-request@lists.debian.org Wed Jan 10 21:03:41 2018
Old-Return-Path	<doko@debian.org>
X-Amavis-Spam-Status	No, score=-4.7 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_LOW=-0.7, REMOVEDOT=3] autolearn=no autolearn_force=no
X-Policyd-Weight	using cached result; rate: -4.2
Old-X-Envelope-From	doko@debian.org
User-Agent	Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version	1.0
Content-Type	text/plain; charset=utf-8
Content-Language	en-US
Content-Transfer-Encoding	7bit
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/15428
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/7ebe8f18-d553-0da6-3556-55e3ebe5c9b1@debian.org
Approved	robomod@news.nic.it
Lines	40
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Wed, 10 Jan 2018 22:02:44 +0100
X-Original-Message-ID	<7ebe8f18-d553-0da6-3556-55e3ebe5c9b1@debian.org>
X-Original-References	<87y3l5y9yc.fsf@debian.org>
Xref	csiph.com linux.debian.maint.python:10033

Show key headers only | View raw

On 10.01.2018 17:06, Ole Streicher wrote:
> Hi,
> 
> I am the maintainer of the "python-astropy" package, that currently
> creates packages for both Python 2 and Python 3. Both packages have a
> number of reverse dependencies.
> 
> Recently, upstream announced a new version 3.0 of astropy, which
> supports Python 3 only, and I think of the best mid-term strategy: The
> old version 2.0 is supported upstream for ~2 years, and I want to have a
> smooth migration path. I checked the wiki, but could not find good
> information about migration.

Currently discussed. See "Python2 EOL and moving towards Python3" on this ML.

> I thought of a temporary package split: create a new source package
> "astropy" that inherits of the current python-astropy package, but only
> builds python3-astropy (and the utils + doc, which depend on
> python3-astropy), and update this to version 3.0. Then I would remove
> these binary packages from the python-astropy package. In parallel, I
> would file bugs (severity: important) to remove the reverse dependencies
> of the Python 2 packages (many of them are mine, but also may have
> reverse dependencies).
> 
> As long as there are substantial problems with the removal of the Python
> 2 support, I then keep the "old" python-astropy package updated. Once
> everything is figured out and we decide to finally kick out Python 2
> support (from Debian-Astro, or from Debian), I would set the remaining
> bugs as RC, and (once they are solved) remove the "python-astropy"
> package.
> 
> Does this sound reasonable? And how should I do this technically?

well, astropy is not such a mainstream package that I would mind removing some
of it's reverse dependencies.  If you want to add the additional pain having a
separate Python2 source stack, go for it. I wouldn't want to do that myself.  If
not, just go ahead with Python3 after having identified the reverse dependencies
which are not maintained by yourself.

Matthias

Thread

Python 2 removal strategy Ole Streicher <olebole@debian.org> - 2018-01-10 17:30 +0100
  Re: Python 2 removal strategy Matthias Klose <doko@debian.org> - 2018-01-10 22:10 +0100
    Re: Python 2 removal strategy "eamanu15 ." <emmanuelarias30@gmail.com> - 2018-01-10 23:30 +0100
  Re: Python 2 removal strategy Stuart Prescott <stuart@debian.org> - 2018-01-11 01:20 +0100

csiph-web