From: Patrick McLean <chutzpah@gentoo.org>
To: "Mike Gilbert" <floppym@gentoo.org>, "Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-python <gentoo-python@lists.gentoo.org>,
python <python@gentoo.org>
Subject: Re: [gentoo-python] Re: [RFC] Timeline for Python 3.6 adoption
Date: Fri, 27 Apr 2018 17:56:27 -0700 [thread overview]
Message-ID: <03034e26-8091-415a-f71f-89d2d3f2f9bf@gentoo.org> (raw)
In-Reply-To: <CAJ0EP42vBPF644TcrssK=F1fpySxRsTvEf2bea870KnSi1dOFQ@mail.gmail.com>
On 2018-04-27 09:05 AM, Mike Gilbert wrote:
> On Fri, Apr 27, 2018 at 9:03 AM, Michał Górny <mgorny@gentoo.org> wrote:
>>
>> Firstly, I'd like to do two changes simultaneously to reduce --newuse
>> rebuilds:
>>
>> a. switching from CPython 3.5 to 3.6,
>>
>> b. disabling CPython 3.4.
I assume you mean remove from the default PYTHON_TARGETS, not disable it
completely? I would wait until after python 3.4 is no longer getting
updates before removing it from the eclass and the tree.
>>
>> I'm thinking of a soft deadline on 2018-06-01, i.e. giving developers
>> a full month to prepare. If things don't go well, we can always
>> postpone it.
>>
>> According to my lists, we only have 6 packages relying on py3.4 right
>> now [1] and no pending stabilizations for that. I will report bugs for
>> those packages today.
>>
>> The list for 3.5->3.6 migration is longer [2]. However, it seems that
>> many of those packages are rather isolated [3] and apparently
>> unmaintained. Apparently the biggest targets are OpenStack
>> and Flask. It's all doable.
>>
>> What do you think?
>
> June 1 seems a little optimistic to me, but as you said we can push it
> out if needed.
>
> This plan makes sense to me.
>
next prev parent reply other threads:[~2018-04-28 0:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 13:03 [gentoo-python] [RFC] Timeline for Python 3.6 adoption Michał Górny
2018-04-27 16:05 ` [gentoo-python] " Mike Gilbert
2018-04-28 0:56 ` Patrick McLean [this message]
2018-04-28 7:00 ` Michał Górny
2018-05-09 20:30 ` Patrick McLean
2018-05-15 5:23 ` Michał Górny
2018-04-28 0:56 ` Patrick McLean
2018-05-15 5:23 ` [gentoo-python] " Michał Górny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=03034e26-8091-415a-f71f-89d2d3f2f9bf@gentoo.org \
--to=chutzpah@gentoo.org \
--cc=floppym@gentoo.org \
--cc=gentoo-python@lists.gentoo.org \
--cc=mgorny@gentoo.org \
--cc=python@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox