Helmut Jarausch wrote: > Up to a few days ago I had > > PYTHON_TARGETS="python3_8" > > in /etc/portage/make.conf > > and for any package to be installed for Python2.7, I had something like > media-gfx/cropgui python_targets_python2_7 > > in /etc/portage/package.use > > But now, I have to add python2_7 to PYTHON_TARGETS whenever I want to > emerge a package which needs Python2.7 > > But keeping > PYTHON_TARGETS="python3_8 python2_7' > in my make.conf > will install an (additional) Python2.7 version whenever the package has > python2_7 in PYTHON_COMPAT in its ebuild file. > > Furthermore I would have to add more and more > > -python_targets_python2_7 > in /etc/portage/package.use > > for any package which does not support Python2.7, any more. > > I am on the 17.1 desktop profile and use the GIT version of portage. > > What has changed and what can I do about it? > > Many thanks for a hint, > Helmut >
I posted about this earlier, in the wrong thread tho. Anyway, I subscribe to -dev and it seems they are starting to remove python 2 support, even tho some or even most things will still work for a while longer. It caused quite a bit of controversy. There is actually a couple threads about it. The best I can come up with, start figuring out a way to keep python 2 around on your own, use a overlay if one is available or start expecting python 2 to disappear, real soon. It seems the devs want it gone even before it's end of life. Dale :-) :-)
