Re: Python 3.13 and massive USE flag changes.

Michael <[email protected]> Sat, 06 Jun 2026 09:26:28 +0100
Newsgroups gmane.linux.gentoo.user
Message-ID <[email protected]>
--nextPart5inDTXVyRpKB7Bp3a0690g
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="utf-8"; protected-headers="v1"
From: Michael <[email protected]>
To: [email protected]
Reply-To: [email protected]
Subject: Re: [gentoo-user] Python 3.13 and massive USE flag changes.
Date: Sat, 06 Jun 2026 09:26:28 +0100
Message-ID: <[email protected]>
In-Reply-To: <[email protected]>
References: <[email protected]>
MIME-Version: 1.0

On Saturday, 6 June 2026 08:50:26 British Summer Time Dale wrote:
> Howdy,
> 
> 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.  When I did the first one and ran emerge -auDN world
> again, it spit out a slightly longer list to add.  I added those as
> well.  Then when I ran emerge again, I got even more packages that
> have to be added.  I checked the recent news items, in case I missed
> one or something, and I found one that I guess I thought didn't need
> to be done right away or something.  The title of the news item is
> Python 3.14 to become the default on 2026-06-01.  Note the date it
> goes into effect.
> 
> So, if someone reading this runs into this, go find that news item. It
> seems you missed it like I did.  It's odd, usually when a news item
> comes out, I follow it right then since I'm doing the updates anyway.
> Something somewhere either got missed on my part or my brain just
> didn't register it because of the future date it would happen.
> 
> Anyway, mostly a heads up for anyone else running into this and
> wonder, what the heck is going on.  ROFL

I've updated a number of systems here and the python upgrade to 3.14 
took place as part of it without any issue, just by running 'emerge 
-uaNDv @world' as I usually do.  The previous python upgrade from 3.13 
was also seamlessly change managed by portage.  Each time a number of 
packages had to be rebuilt with the later python version, without manual 
intervention.  This is probably because I have not set PYTHON_TARGETS or 
PYTHON_SINGLE_TARGET in /etc/portage.

Have you had bespoke python versions specified in your system?


> I do have one question.  I build my packages in a chroot.  I wonder
> how I need to do that?  Can I do the whole switch in a chroot and
> then copy the binaries over or do I need to do the first part, copy
> the binaries over, do the second part and copy those over in two
> separate stages? Should this be a one stage or two stage update on my
> running OS I guess is what I'm asking.
> 
> Dale
> 
> :-)  :-)

I would update/upgrade the binhost system in the chroot.  Python, 
portage and many more packages will be brought up to date.

Then use the updated/upgraded binaries from you chrooted binhost to 
update the running OS as you normally do.  Run emerge with '--usepkg y' 
instead of '--usepkgonly y' so the OS can build its own packages if/when 
the chrooted binaries won't do.

If you have specified some earlier python slot in either system, then 
you'd have to address this configuration as explained in the news item.

That's how I would go about it, but since our Gentoo systems are not the 
same YMMV.  :-)
--nextPart5inDTXVyRpKB7Bp3a0690g
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iQJPBAABCAA5FiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmoj2bQbFIAAAAAABAAO
bWFudTIsMi41KzEuMTIsMiwyAAoJELHqqvbClWcZm5EP/2slajonWcY8gO/sWzNX
x+Zqcu72j+LfTPLO4NJwLLHMaZ1t9+bsJq1JA16NpJPOlZPnjxDq85TJbNWaSsGx
dm927afE+GzHpac2JD42PKbvvC/mFKi9zy4wVqGifRNAOnq1oTRlqFkwj/BHQFmI
NRXglGrliu7OFzKSmck6DUX5Y2g+ldfHmoNRqJZGtoPVxk/LqWl3JLYWSBDSb+Z0
cY2mi2yub6m/2JLMH6Fj3h9Kxajzc10roxxNNpGUFWsy75RNboaEI6uxxIz7eEkd
5NUwbgHmjYftTbjuMVuLaWiS3tfOEdGf+UR5R1BhlI2xbtzd6ngolOONjXRnGsOH
vvdLfeJchOFtP74SWbvd3yz2nk2Q2GuLBBY7KoV/MZHmJkMUYsHL6mlAqYRZUWp3
oyJrV8L73dARutwKCHgQwLBi71XW9Jg53KeOOJDGgnZXxrrsu6H2w0z2+Z1E/9j0
DlNLv+u165KozkXswi5/IsL+9J2W2z7Vmr/rM+3+pTLUqYDguXfnn04B17/9ZNUk
pmA80V/tKRNDo/JBp6zqm1UUkznJFeeIK9IxNqGY4yo6BY7qa+rFxqGFpEKjl1Vs
FgrRFQ1yVTUcIQTvquutlMhN/kvx8XUDcEMhbZou+65uAwYHKtqKkxv7X6G7Btp/
zLHRcyrki3fGIxcir+fesVJL
=uUAW
-----END PGP SIGNATURE-----

--nextPart5inDTXVyRpKB7Bp3a0690g--