Re: Python 3.13 and massive USE flag changes.

On Sat, Jun 6, 2026 at 11:25=E2=80=AFAM Michael Orlitzky <[email protected]> w=
rote:
>
> On 2026-06-06 02:50:26, Dale wrote:
> > I'm trying to do my weekend updates. At first, I got one or two
> > packages that wanted me to put in the package.use file to use Python
> > 3.13, some only want one to be used so I had to also disable other
> > python versions.
>
> This happens every time. If some packages don't add python-3.14
> support before 3.14 is made default, portage will tell you to do
> outrageous things to fix it, and they won't work. Overlay packages
> are especially bad in this regard.

Yeah. I did actually manage a combination of USE overrides for
PYTHON_SINGLE_TARGET/PYTHON_TARGETS for the couple of overlay packages
I have that are stuck on 3.13, but I also have convinced all but one
(so far) to add 3.14 support, so _most_ of my nightmare is gone.

For me it was termux-language-server and autotiling (both GURU
packages). The latter has had no response or update yet.

> The first thing I would try is to remove any python-related settings
> from your package.use and make.conf (just comment them out). Remove
> any packages that are from overlays, and try a -uDN @world update. If
> that doesn't work... wait a week and try again. If that doesn't
> work... then maybe it's worthwhile to investigate what portage is
> trying to tell you.
>
> If you don't have any packages stuck on python-3.13, the upgrade
> should work with no hassle. If you do, portage will spit out something
> insane, and you have to try to ignore it :)

Some of the conflict messages were indeed messy, but the required 3_13
use flag messages were not horrible.

--=20
D. Ben Knoble