| 1 |
On 2018-04-27 09:05 AM, Mike Gilbert wrote: |
| 2 |
> On Fri, Apr 27, 2018 at 9:03 AM, Michał Górny <mgorny@g.o> wrote: |
| 3 |
>> |
| 4 |
>> Firstly, I'd like to do two changes simultaneously to reduce --newuse |
| 5 |
>> rebuilds: |
| 6 |
>> |
| 7 |
>> a. switching from CPython 3.5 to 3.6, |
| 8 |
>> |
| 9 |
>> b. disabling CPython 3.4. |
| 10 |
|
| 11 |
I assume you mean remove from the default PYTHON_TARGETS, not disable it |
| 12 |
completely? I would wait until after python 3.4 is no longer getting |
| 13 |
updates before removing it from the eclass and the tree. |
| 14 |
|
| 15 |
>> |
| 16 |
>> I'm thinking of a soft deadline on 2018-06-01, i.e. giving developers |
| 17 |
>> a full month to prepare. If things don't go well, we can always |
| 18 |
>> postpone it. |
| 19 |
>> |
| 20 |
>> According to my lists, we only have 6 packages relying on py3.4 right |
| 21 |
>> now [1] and no pending stabilizations for that. I will report bugs for |
| 22 |
>> those packages today. |
| 23 |
>> |
| 24 |
>> The list for 3.5->3.6 migration is longer [2]. However, it seems that |
| 25 |
>> many of those packages are rather isolated [3] and apparently |
| 26 |
>> unmaintained. Apparently the biggest targets are OpenStack |
| 27 |
>> and Flask. It's all doable. |
| 28 |
>> |
| 29 |
>> What do you think? |
| 30 |
> |
| 31 |
> June 1 seems a little optimistic to me, but as you said we can push it |
| 32 |
> out if needed. |
| 33 |
> |
| 34 |
> This plan makes sense to me. |
| 35 |
> |
Archives