sam's going to test if libxcrypt upgrade goes cleanly now, and CC arches then.
Okay, I haven't seen any issues since I dropped 3.10 from PYTHON_COMPAT in glibc. I think we want to stable this now to maximise the number of people who have this installed before we have to flip target defaults (and ofc that means having it in glibc too). (Portage copes better with the libxcrypt/python/glibc circular dep if there's at least one Python that is useful that it's going to keep, because you can --exclude the newer ones temporarily.) Small chance we'll need to drop keywords back to ~arch but I really don't expect to need to do this.
amd64 done
arm64 done
x86 done
arm done
ppc done
ppc64 done
sparc done
hppa done, bug done