On Tue, Jun 4, 2024 at 9:14 AM Rich Freeman <ri...@gentoo.org> wrote: > > On Tue, Jun 4, 2024 at 11:40 AM Joost Roeleveld <jo...@antarean.org> wrote: > > > > Those steps do not just work. > > The news item actually specifically states that portage will "just do > > the update" if you have not set any python_targets stuff. > > I have those not set, but it fails on ALL my systems. > > > > There are also still over 280 packages that are STILL not supporting > > python 3.12 according to bugs.gentoo.org. > > That probably isn't even all of them. On Sat somebody pointed out bug > 933383 which isn't even linked to the tracker. I'm sure it would have > been, but I probably closed it before it got that far. > > I don't want to be too picky as the core language maintainers have A > LOT of work to do, but part of the challenge is that it isn't very > obvious to a package maintainer (or anybody else) what packages > actually have problems.
Even though I don't Gentoo anymore I can relate that the same problems exist for other distros. My work on Kubuntu ran into Python problems when they updated to 3.12.3. The system works, as best I can tell, but a library I use (endplay) doesn't. What I learned is, prior to a new major update on my coding machine, is to build a Virtualbox VM of the new Kubuntu version and do testing in that first. (Far more practical for me on Kubuntu than you guys on Gentoo.) If all the libraries work, then great, but if not then in this case I had to build a 3.11 python virtual environment and work in there until the library maintainers catch up. I suspect in the case of the OP that it's possible that many of the python libraries possibly aren't part of the base system but rather things that got loaded over the years and along the way?
