Hi all,
We should get started on Python 3.12, 3.13 alpha is already getting
released!
To be 100% honest, I am not super looking forward to it as it's a ton of
work due to our lack of automated tooling. In basics a plan would be to
first tackle low hanging fruit to-do's:
* https://archlinux.org/todo/pytest-runner-removal/
* https://archlinux.org/todo/imp-module-removal-in-python-312/
* https://archlinux.org/todo/use-pyprojecttoml-for-building-if-supported/
* drop unused python modules in our repo
https://archlinux.org/devel/reports/unneeded-orphans/
We've finished python-bootstrap, and can bootstrap the required build
packages (python-setuptools, build, etc.). And figuring out the rebuild
order. (Big thanks to david, for the help here!) [1] [2]
So soon we can start the rebuild which will probably take a while to
complete as we have no good automated tooling yet for mass rebuilds.
This rebuild will likely block [staging] for a good 2 or more weeks, so
when would be a good time to schedule this?
I expect two things to break our package builds in 3.12:
* The removal of distutils see the snippet below, adding
python-setuptools to makedepends should resolve this. For example:
GISCAN ZBar-1.0.gir
Traceback (most recent call last):
File "/usr/bin/g-ir-scanner", line 99, in <module>
from giscanner.utils import dll_dirs
File "/usr/lib/gobject-introspection/giscanner/utils.py", line 385,
in <module>
import distutils.cygwinccompiler
ModuleNotFoundError: No module named 'distutils'
* The removal of the imp module, the todo list above has been open for a
while, but not all packages have been fixed.
* The usual failing tests, missing sources you know it :)
[1]
https://gitlab.archlinux.org/archlinux/python-bootstrap/-/merge_requests/3
[2] https://notes.vdwaa.nl/arch/python.html
Greetings,
Jelle
