Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From: Nicholas D Steeves <nsteeves@gmail.com>
Newsgroups: linux.debian.maint.python
Subject: Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream
Date: Mon, 14 Oct 2019 05:50:01 +0200
Message-ID: <yQZwR-64v-1@gated-at.bofh.it>
References: <yQZwR-64v-3@gated-at.bofh.it>
Old-Return-Path: <nsteeves@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Approved: robomod@news.nic.it
Lines: 70
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:11883

--=-=-=
Content-Type: text/plain

Hi Thomas and Python Team,

Thomas Goirand <zigo@debian.org> writes:

> For example, today I looked into removing Python 2 from python-cogent.
> Running sixer on all files lead to a huge log of problems to solve by
> hand. There's no upstream support for Python 3 on that one.
>
> For this kind of package, I see no way out except:
> - Upstream works on Python 3 support
> - Someone in Debian makes the effort
>
> But in both cases, it's going to take a very long time. Do we really
> want to get stuck on these packages for like forever, or would it feel
> ok to raise the severity to serious, so that the package gets
> auto-removed and then we can work on removing Python 2 from its
> dependencies?

It seems to me that a fair and conservative solution is to send an
announcement once a month that all Python 2 packages will have an RC bug
filed against them on 1 January 2020.  I work on the Calibre package,
and depend on it for my daily work.  I do not believe that its reverse
deps should be removed before 1 Jan 2020.

As far as the maximum number of announcements, how about: the first
announcement ASAP, the second one 1 Nov, then 1 Dec.  Lets CC this
announcement to devel, -python, -med, and any other teams with a
significant number of Python packages.

The issue is similar to global warming.  People will hide their head in
the sand singing "nah nah nah, it's not real, I don't have to deal with
it" until a tipping point occurs.

Honestly part of me wonders if RedHat/IBM is going to maintain Python 2,
like they did with Java.

  https://developers.redhat.com/blog/2018/09/24/the-future-of-java-and-openjdk-updates-without-oracle-support

Barring that hypothetical possibility, I still think the right thing to
do is file RC bugs the 1 of January.  What happens then?  My guess is
upstreams start containerising their py2 software and someone will write
a helper script like py2-zombie-flatpack.


Cheers,
Nicholas

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE4qYmHjkArtfNxmcIWogwR199EGEFAl2j7nIACgkQWogwR199
EGGbpRAA2KUYc7KKgktyfLAJ3QzkxTMTI8ChN7DlSpWw/SAajdka2aM7Uml6VxsG
44QcGgyRDD8gInlpeNRzxHB6DQIjrPcTSHRUTjUMVr6LII00fJKKCoEHcg5u80py
d6fvnG+LJqJUNo2sjYWVTwzKPwYeKqJDc8WqKR8ZYWFMo1XAUW721Z2FTrf8Oeui
WJoZvsdIeRFmvvILDVWrMwl3W1/uxCPTSQjMwh2TBBY0552OGPkL/1ZHuqX/apqp
t3Qw24+enu308GLZsGChOph5k3kJ6sfcFqgY2hK94etKW8IxKlq4z4hE+TsqMxDE
ONNAd/30SOR+axmgVL9vkJFgw1f0dGfG51OZWyoNW/1on9N08WqUG1lSPT6EvXR5
nSmO70uSRKMcCeQPqeY0OgppT9IKxQbfw72KLZiYcfccU03I8SJo6qsSv97PY1xW
CyzJX4GTlxT1eelYVafHq1S6v7BtKQxjJAAHKlvbEsbpbeX5lLiCn8vnn8Kk0vBt
x2tjXZCEt8aVL2rznqEZvA9Kt7FCJfxAPolVJQqBg0idw7+QiZ72Xt7kj6ggRjCa
/o5okCf2+f/bqqBtrDgtdt8/dBYT64WsYhCARqqrUyNkRWHj39wpUhAsnFX5JIzN
KhOyyuKgYu0fBsWSdhfQWdRRcbsPtWJWQCzML+kw/Ga6AJYR+Tk=
=TibC
-----END PGP SIGNATURE-----
--=-=-=--