On Fri, Apr 27, 2018 at 9:03 AM, Michał Górny <[email protected]> wrote: > Hi, everyone. > > I think we've reached the point where we should start discussing > switching the defaults to Python 3.6. I would like to gather your > opinion the following ideas. > > 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'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.
