1 |
> |
2 |
> |
3 |
> On 11 Nov 2021, at 18:40, Patrick McLean <chutzpah@g.o> wrote: |
4 |
> |
5 |
> On Thu, 11 Nov 2021 12:58:24 -0500 |
6 |
> "Wolfgang E. Sanyer" <wolfgangesanyer@×××××.com> wrote: |
7 |
> |
8 |
>> El jue, 11 de nov. de 2021 12:56 p. m., Patrick McLean <chutzpah@g.o> |
9 |
>> escribió: |
10 |
>> |
11 |
>>> On Thu, 11 Nov 2021 17:05:45 +0100 |
12 |
>>> Michał Górny <mgorny@g.o> wrote: |
13 |
>>>> I'd like to add some dates regarding 3.8 removal and 3.10 switch to |
14 |
>>>> the implementation timeline [1]. |
15 |
>>>> |
16 |
>>>> Unless I'm mistaken, CPython is following a yearly release cycle these |
17 |
>>>> days. I think it would make sense to also aim for a yearly cycle |
18 |
>>>> in Gentoo, i.e. roughly switch to the next minor version every year. |
19 |
>>>> |
20 |
>>>> Hence my proposal would be to: |
21 |
>>>> |
22 |
>>>> a. ASAP: send "please port your packages to py3.9" mail |
23 |
>>>> |
24 |
>>>> b. 2022-06-01: remove py3.8 target |
25 |
>>> |
26 |
>>> Could we please push this back, I would prefer some time in 2023 if |
27 |
>>> possible. |
28 |
>>> |
29 |
>> |
30 |
>> Is there a particular reason you wish to push it back, or is it purely |
31 |
>> personal preference? |
32 |
>> |
33 |
> Professional preference? My employer (which employs several Gentoo |
34 |
> developers, and funds a large amount of Gentoo work) needs a bit more |
35 |
> time to migrate all the internal stuff to 3.10. |
36 |
> |
37 |
> |
38 |
|
39 |
I think this is fair but if you do need something for work, please say that |
40 |
so we don't need to guess / think it might be for your personal capacity. |
41 |
|
42 |
I also think it's probably worthwhile to offer upfront help if needed if you |
43 |
can. |
44 |
|
45 |
That said, I agree! |
46 |
|
47 |
I think we need to push it back a little bit to ease upgrades (see |
48 |
the recent thread) but also to help downstreams like Flatcar OS |
49 |
which are still migrating away from Python 3.8. |
50 |
|
51 |
I don't mind chipping in to help. |
52 |
|
53 |
[There is a separate issue with stabilising the Python 3.10 |
54 |
interpreter. I'd like this done as soon as it's ready (and it works |
55 |
fine here), but there's a problem with circular dependencies |
56 |
and python-any-r1 dragging it in on upgrades and causing issues with libxcrypt.] |
57 |
|
58 |
Best, |
59 |
sam |