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