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

Python 2 removal strategy

Path	csiph.com!goblin2!goblin.stu.neva.ru!news.unit0.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From	Ole Streicher <olebole@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Python 2 removal strategy
Date	Wed, 10 Jan 2018 17:30:03 +0100
Message-ID	<v6rqj-4sq-23@gated-at.bofh.it> (permalink)
X-Original-To	debian-python@lists.debian.org
X-Mailbox-Line	From debian-python-request@lists.debian.org Wed Jan 10 16:24:09 2018
Old-Return-Path	<news@liska.ath.cx>
X-Amavis-Spam-Status	No, score=-6.751 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.249, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no
X-Policyd-Weight	using cached result; rate: -7
User-Agent	Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
MIME-Version	1.0
Content-Type	text/plain
Lines	33
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/15426
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/87y3l5y9yc.fsf@debian.org
Approved	robomod@news.nic.it
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Wed, 10 Jan 2018 17:06:51 +0100
X-Original-Message-ID	<87y3l5y9yc.fsf@debian.org>
Xref	csiph.com linux.debian.maint.python:10031

Show key headers only | View raw

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.

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?

Best regards

Ole

Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar | Unroll thread

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