On Sat, 2025-12-20 at 16:13 +0100, Michał Górny wrote: > On Thu, 2025-12-04 at 19:34 +0100, Michał Górny wrote: > > Hello, everyone. > > > > Just a heads up: Django 6.0 (already released) and NumPy 2.4.0 (at rc1) > > are removing Python 3.11 support. They're not the first packages to do > > that, but they are the ones that will have some major impact. > > > > Now dev-python/sphinx (RC) joined the list, and this is becoming > a growing nuisance. That said, there's still a few packages that > require Python 3.11 explicitly. I've last-rited these with no relevant > activity today. > > The main problem is a huge number of reverse dependencies. Admittedly, > for many of them I could just revbump or otherwise provide an upgrade > path, but given the number, it's a lot of work, and I don't see much > benefit to it. > > So the way I see it, we have two options: > > 1. I spent a lot of effort aggressively removing Python 3.11 from > reverse dependencies of these packages, and leave Python 3.11 support > where it still can be kept. > > 2. I remove Python 3.11 everywhere except for the few packages that > still need it. > > I think at this point 2. is much less work, and I don't see much reason > to go through the humongous effort for 1. The second option will also > mean removing PyPy3.11 support entirely.
Small update: it turned out 2. is actually more work, because of all the dependency hell involved in setuptools and packages' tests. I've ended up going the revdep route, and it took around 2 hours, but now dev- python/django and dev-python/sphinx are 3.12+ only. -- Best regards, Michał Górny
signature.asc
Description: This is a digitally signed message part
