In prep for a changeover to using Python 3.11 by default, I've done a couple of rounds of bulk builds with the default Python version setting to 3.11. Debian already uses 3.11 as the main version in a stable release (bookworm), the ecosystem is in fairly good shape already.
I've fixed a few problems that can be fixed in advance without too much churn. As usual there are a few minor PLIST and library version number things to update. Otherwise most of the ports tree builds. Remaining build-time issues: - math/py-tables: needs a newer version for py3.11 support, but that also requires blosc2 (either as a separate port, or update archivers/blosc to blosc2 if the rest of the related chain of ports is happy). Has anyone already looked at updating this? - devel/py-lief: looks like an update will fix it, but upstream no longer provides an sdist. It should be possible to build from git, but needs additional ports to build, and often wants very specific versions, making it a pain to handle in ports. There have been no actual port updates since 2021 (despite fixes for a dozen CVEs in this reverse engineering tool). I think at this point removing the port might make the most sense. - www/py-cookies: pining for the fjords (last commits Sept 2014), not used in ports. ... Build was done on i386 so there could still be failures in amd64-only ports (and a bulk on amd64 would be handy at some point, though let's get known things fixed first). There could of course be runtime problems, so sometime soonish would be a good point in the release cycle to switch over so we can shake them out.
