Python 3.13 and massive USE flag changes.

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 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

:-)  :-)