1 |
On 1/12/2020 17:17, David Seifert wrote: |
2 |
> On Sun, 2020-01-12 at 17:07 -0500, Joshua Kinard wrote: |
3 |
>> On 12/5/2019 09:24, Rich Freeman wrote: |
4 |
>>> On Thu, Dec 5, 2019 at 8:59 AM Jason A. Donenfeld <zx2c4@g.o |
5 |
>>>> wrote: |
6 |
>>>> It's quite another to mask random packages that have USE flags to |
7 |
>>>> optionally support whatever python 2.7 library. If you're going |
8 |
>>>> to |
9 |
>>>> last rites these, talk with the maintainer first, and only then, |
10 |
>>>> send |
11 |
>>>> emails one at a time. Doing that en masse isn't appropriate. |
12 |
>>> |
13 |
>>> ++ - I have no idea if that happened. For anything USE-controlled |
14 |
>>> it |
15 |
>>> would make more sense to file a bug or mask the package-flag combo |
16 |
>>> itself. |
17 |
>>> |
18 |
>>>> On another topic, I'd prefer for python 2.7 not to be removed |
19 |
>>>> from |
20 |
>>>> gentoo. Tons of code still uses it. |
21 |
>>>> |
22 |
>>> |
23 |
>>> I'm sure a million people would share that preference. I'm not |
24 |
>>> sure |
25 |
>>> what the upstream/security status is of 2.7. Obviously to keep it |
26 |
>>> around it would need to be reasonably secure, and somebody within |
27 |
>>> Gentoo would have to want to maintain it. That's basically the |
28 |
>>> criteria for keeping anything like this around. If somebody |
29 |
>>> stepped |
30 |
>>> up and said "I'm maintaining 2.7 and here is why it will remain |
31 |
>>> secure..." I doubt they'd get a lot of resistance. |
32 |
>>> |
33 |
>> |
34 |
>> I'm late to the party as usual. Seems upstream plans a final 2.7.18 |
35 |
>> security update in April of 2020, then they will consider the 2.7 |
36 |
>> branch |
37 |
>> EOL. They say most of these updates were done in 2019, and so are |
38 |
>> still |
39 |
>> technically sticking to their mantra of no more updates after |
40 |
>> 01/01/2020. |
41 |
>> |
42 |
>> PEP 373 covers this: |
43 |
>> https://www.python.org/dev/peps/pep-0373/#release-schedule |
44 |
>> |
45 |
>> """ |
46 |
>> Planned future release dates: |
47 |
>> |
48 |
>> 2.7.18 code freeze January, 2020 |
49 |
>> 2.7.18 release candidate early April, 2020 |
50 |
>> 2.7.18 mid-April, 2020 |
51 |
>> """ |
52 |
>> |
53 |
>> IMHO, I think we should retain 2.7.x compatibility for 1 year AFTER |
54 |
>> the |
55 |
>> release of 2.7.18. This provides some time for people to transition |
56 |
>> systems |
57 |
>> off of 2.7-dependent packages. |
58 |
>> |
59 |
>> It might be worthwhile to treat the removal of Python-2.7 from the |
60 |
>> tree in |
61 |
>> the same manner as an EAPI deprecation and removal, given how |
62 |
>> ingrained it |
63 |
>> is due to its longevity. That will minimize the whiplash-effect of |
64 |
>> emerge |
65 |
>> complaining about slot conflicts and dependency conflicts. Like I |
66 |
>> just ran |
67 |
>> into w/ setuptools-45.0.0.0's release. |
68 |
>> |
69 |
> |
70 |
> Thanks for volunteering to help us manage the ton of packages that have |
71 |
> dropped py2 in the mean time. I wasn't aware you were part of the |
72 |
> python team, but I must have been mistaken! |
73 |
|
74 |
I'm not, heh. But I have noticed the increasing difficulty of getting |
75 |
emerge to do clean updates recently because of these removals, especially |
76 |
when you go several weeks between --sync updates on a machine. The status |
77 |
of py2 removal does not seem to have been communicated really well, nor any |
78 |
kind of plan agreed upon, like we've done w/ the EAPI removal. |
79 |
|
80 |
If I had more time outside of work, I'd love to help. But it's a struggle |
81 |
enough right now to keep my systems ~arch updated, especially since my MIPS |
82 |
boxes aren't exactly speed demons. Right now, I'm just suggesting that |
83 |
maybe we should apply the brakes a little bit and try to coordinate how to |
84 |
remove py2 completely, rather than the way it's being done now. |
85 |
|
86 |
-- |
87 |
Joshua Kinard |
88 |
Gentoo/MIPS |
89 |
kumba@g.o |
90 |
rsa6144/5C63F4E3F5C6C943 2015-04-27 |
91 |
177C 1972 1FB8 F254 BAD0 3E72 5C63 F4E3 F5C6 C943 |
92 |
|
93 |
"The past tempts us, the present confuses us, the future frightens us. And |
94 |
our lives slip away, moment by moment, lost in that vast, terrible in-between." |
95 |
|
96 |
--Emperor Turhan, Centauri Republic |