| 1 |
W dniu śro, 09.05.2018 o godzinie 13∶30 -0700, użytkownik Patrick McLean |
| 2 |
napisał: |
| 3 |
> |
| 4 |
> On 2018-04-28 12:00 AM, Michał Górny wrote: |
| 5 |
> > W dniu pią, 27.04.2018 o godzinie 17∶56 -0700, użytkownik Patrick McLean |
| 6 |
> > napisał: |
| 7 |
> > > On 2018-04-27 09:05 AM, Mike Gilbert wrote: |
| 8 |
> > > > On Fri, Apr 27, 2018 at 9:03 AM, Michał Górny <mgorny@g.o> wrote: |
| 9 |
> > > > > |
| 10 |
> > > > > Firstly, I'd like to do two changes simultaneously to reduce --newuse |
| 11 |
> > > > > rebuilds: |
| 12 |
> > > > > |
| 13 |
> > > > > a. switching from CPython 3.5 to 3.6, |
| 14 |
> > > > > |
| 15 |
> > > > > b. disabling CPython 3.4. |
| 16 |
> > > |
| 17 |
> > > I assume you mean remove from the default PYTHON_TARGETS, not disable it |
| 18 |
> > > completely? I would wait until after python 3.4 is no longer getting |
| 19 |
> > > updates before removing it from the eclass and the tree. |
| 20 |
> > |
| 21 |
> > I meant disabling it completely. The default is 3.5 for a long time |
| 22 |
> > already, and there is no reason to expect people to go back and test |
| 23 |
> > their packages against 3.4. The plan was to support only one Python 3.x |
| 24 |
> > release behind current stable.>>>> |
| 25 |
> > > > > I'm thinking of a soft deadline on 2018-06-01, i.e. giving developers |
| 26 |
> > > > > a full month to prepare. If things don't go well, we can always |
| 27 |
> > > > > postpone it. |
| 28 |
> > > > > |
| 29 |
> |
| 30 |
> IMHO, it would be better to wait until upstream deprecates Python 3.4 |
| 31 |
> before we disable/drop it. There are downstreams (my employer for one, |
| 32 |
> and I am sure we are not the only ones) that are still using it, and |
| 33 |
> have plans in place to migrate by the upstream deprecation date. |
| 34 |
> |
| 35 |
|
| 36 |
Agreed. I'll also include its deprecation date in the announcement |
| 37 |
to remind people. |
| 38 |
|
| 39 |
-- |
| 40 |
Best regards, |
| 41 |
Michał Górny |
Archives