TL;DR: Please help triage and forward 3.13 bugs. Help upstreams to port
to 3.13.
Python 3.13 is due to release at the start of October [0]. I think we'd
like it to be the Python version in trixie.
[0]:
https://peps.python.org/pep-0719/
I've done a fairly large rebuild of Python packages with Python 3.13rc2 available as a supported version on debusine.debian.net arm64 buliders.
Results:
Success: 4605
Failure: 545
Error: 4
I've filed around 100 Debian bugs [1]. The rest of the failures are: unreachable due to Build-Depends that aren't working on 3.13 yet,
existing FTBFS, and packages that don't build on arm64.
[1]:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-python@lists.debian.org&tag=python3.13
There are probably a good number of packages with issues with 3.13 that
haven't been uncovered yet, but this is enough to get moving.
Many of these issues are tracked upstream. I marked them forwarded when
I could see that. Many aren't. It would be useful to reproduce these
issues on upstream git HEADs, under tox / whatever, and forward these
issues upstream. It would be extremely useful to submit patches upstream
to port to 3.13.
FWIW, my test rebuild used manual bootstraps of nodoc+nocheck builds of:
* astropy
* matplotlib
* numpy
* pandas
* protobuf
* pycxx
* scikit-learn
* scipy
* skimage
The results weren't all installable, I think we weren't able to build
things requiring scikit-learn or astropy. I didn't dig into that too
deeply. If anyone would like to poke at this test setup, I can show you
what I used.
Stefano
--
Stefano Rivera
http://tumbleweed.org.za/
+1 415 683 3272
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)