On Sat, Feb 24, 2018 at 12:50 PM, M. J. Everitt <m.j.everitt@iee.org>
wrote:
>
> So, all that remains is who's gonna do the work - both on the
> stabilisation of python3.6 as a dev-lang package, and all the associated
> (thousands?) of dev-python packages?
> You may have brought Zac on board on the portage side of things, but what
> about the rest?
>

Good question, here is the answer.

Standardizing on 3.6+ support for Portage does not require Gentoo to get
rid of 2.7.

The thousands? of ebuilds that need 2.7 continue to need 2.7.

Dropping support for 2.7 also doesn't require ANY code changes to Portage.
It is a strategic decision to not *continue* to maintain 2./7 support in
the future if *it becomes an annoyance or limitation* for us to do so. In
some areas, we are finding that it is.

Also, on a side-note, I have been personally helping Gentoo with the effort
of removing pycrypto dependencies from Python modules.

-Daniel