On Sun, 2020-09-27 at 11:08 -0700, Alec Warner wrote: > On Sun, Sep 27, 2020 at 10:45 AM Michał Górny <[email protected]> wrote: > > > Hello, everyone. > > > > TL;DR: we're nearing the total annihilation of Python 2 software > > in Gentoo. Most users could safely disable py2 USE flags today. > > Python 2 vulns have been patched recently, the interpreter and a few > > packages using Python at build time (with no deps) will stay. Should we > > change PYTHON_TARGETS now, or wait some more and just annihilate > > the py2 flag from all packages? > > > > > > Long version: > > > > We're reached the point where the majority of packages relying on py2 > > have either been ported to py3, removed or masked for removal. > > As a result, I've been able to eliminate python2_7 target from the vast > > majority of dev-python/* packages. On their next system upgrade, our > > users are going to notice most of Python 2.7 modules gone from their > > systems. > > > > However, because of their reverse dependencies a few packages can't lose > > their py2.7-iness, and therefore are going to block depcleaning Python > > 2.7 for now. These include old versions of setuptools, numpy, pillow, > > as well as all versions of cython, nose, pykerberos, pyyaml and their > > dependencies. The major blockers for them are: > > > > - dev-lang/gdl (py entirely optional but the package itself is seriously > > broken) > > > > - dev-db/mongodb (py3 version was just stabilized, need to decide how to > > clean old versions up) > > > > - games-engines/renpy (no py3 version yet) > > > > - media-tv/kodi (py3 version in alpha) > > > > We plan to have these packages fixed or removed by the deadline. > > > > > > However, we already know that there are some packages that use Python 2 > > at build time and that will keep requiring it past the deadline. > > The initial list includes: > > > > - dev-python/pypy* (TODO: need to figure bootstrap out) > > > > - dev-lang/spidermonkey, www-client/seamonkey, www-client/firefox... > > (thank you, Mozilla) > > > > - www-client/chromium, dev-qt/qtwebengine... (thank you, Google) > > > > Sadly, the big corps are too busy improving their spying functionality > > and creating NIH programming languages to take care of such minor > > matters as cleaning up. > > > > https://bugs.chromium.org/p/chromium/issues/list?q=Proj%3DPython3Migration&can=2 > is the tracker for python3 migration for chromium. I resent the implication > that Google is 'too busy' to work on it. > > E.g. on > https://bugs.chromium.org/p/chromium/issues/detail?id=941669&q=Proj%3DPython3Migration&can=2 > the last commit was Sept 26, or yesterday ;p >
Do you happen to have some 'starting date' too? -- Best regards, Michał Górny
signature.asc
Description: This is a digitally signed message part
