> I tried removing python2 on a handful of test systems over the last week
> ... it's back everywhere.
>
>
I attempted the same over the last couple of days as I was thinking "It's
going anyway, why not get a head start?". I had to do the following:

* Remove metagen
* Remove rr
* Update kodi and related packages to 9999 (I know they are working on
getting their 19.0 package out asap because of the 2.7 EOL)
* Update clang and related packages to 9.0.0
* Remove python dependency in libdbusmenu (it's not needed, PR here:
https://github.com/gentoo/gentoo/pull/13790)
* Port gnome-doc-utils to python3 (
https://github.com/gentoo/gentoo/pull/13791)
* Remove qt-creator as it depends on clang 8, changing USE to -clang would
also work but not really using it anyway atm
* Remove gconf dep from discord-bin (
https://github.com/gentoo/gentoo/pull/13793)
* Remove gconf dep from spotify (https://github.com/gentoo/gentoo/pull/13794
)
* Update gcr to 3.34.0 (https://github.com/gentoo/gentoo/pull/13798)
* Unmask a number of other packages that luckily did have updated versions
available: samba, talloc, javatoolkit, tdb, tevent, ldb, itstool,
dropbox-cli, nodejs
* Unmerge typing (now provided by python package)
* Reinstall m2crypto, python-typing, scons
* Reinstall crda with patch in https://bugs.gentoo.org/693728
* Manually fix some packages that were not being selected for emerge by -N:
m2crypto, virtual/python-typing, typing, scons

Unfortunately I was not able to completely purge python2.7 from my system.
The base package is still installed as it is required to build qtwebkit,
qtwebengine, zziplib, firefox and spidermonkey. At least however I am now
running with -python_targets_python2_7 so there's that.

br,
Mathy