On 2019-12-05 04:06, William Hubbs wrote: > On Thu, Dec 05, 2019 at 03:56:05AM +0100, Thomas Deutschmann wrote: >> On 2019-12-05 01:15, Aaron Bauman wrote: >>> * Removal in 30 days >> >> Why? I understand that Py2 will reach EOL upstream status but we all >> know that Py2 will *not* disappear and stop working in 26 days... >> >> There's no reason to mask/remove currently known working software. >> >> net-nntp/sabnzbd is a perfect example. Up to date in repository and working.
First, this was just an example. For sabnzbd I know that upstream is working on Py3 support. It will happen somewhere in 2020... I expect this for most software still in use. My point was a general note: I don't understand why we should rush and kick out software without Py3 support *yet* when Py2 is still a thing. Sure, we will reach the point when Py2 is only needed by 1-2 packages and at this point we can start discussing to drop them including entire Py2 support. But this will take 1-2 years... I mean: OpenSSL-1.0.2x will go EOL on 2019-12-31... I don't see us masking <openssl-1.1.x before that date or even months later. It will still be around for quite some time... And I think same is true for Py2. There's also an important difference: Thanks to our Python implementation, you can set your system to use Py3 by default for everything but still keep a slotted Py2 around for stuff which wasn't ported yet. That's not possible for OpenSSL-1.0.2x for example... > Are you volunteering to maintain it or open an upstream bug and askthem > to move to py3? ...and sometimes I am also just a user. I cannot maintain all software I use :-) -- Regards, Thomas Deutschmann / Gentoo Linux Developer C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5
signature.asc
Description: OpenPGP digital signature
