python: Update to 3.13.11

[lazka]

No description provided.

[lazka]

@MehdiChinoune @striezel any objections to starting the Python rebuild sometime today?

[MehdiChinoune]

No objection, I will push just some small updates.

[striezel]

No objections from my side. Let's go ahead.

[lazka]

We are hitting the new release assets count limit. I need to implement some sharding before we can continue.

[lazka]

I've pushed a hacky fix

[MehdiChinoune]

something is broken about path conversion with this update especially with installation, It happens with many packages:
gdal: some files used to be installed in bin are now installed in Scripts (same as MSVC).
libmsym: python module is installed in lib/site-packages instead of lib/python3.13/site-packages.
pyqt5/pyqt6: D:/W/B/pkg/mingw-w64-ucrt-x86_64-python-pyqt6/d/ucrt64/share/qt6/plugins/PyQt6/pyqt6qmlplugin.dll somehow the drive letter /d is inserted.

[lazka]

Likely they force the "nt" scheme, which is no longer patched (??)

Another issue is that with 3.13 "/foo" is no longer considered absolute on Windows (meson was affected by this, and libbotan, resulting in the install path being wrong)

[lazka]

I'll look into the install path issue later. something in setuptools..

[striezel]

libmsym: python module is installed in lib/site-packages instead of lib/python3.13/site-packages.

See #27268 for that. libmsym also needs an extra CMake patch to build. But I stopped working on that, because I couldn't figure out the Python stuff.

I pushed some other fixes for problems that showed up during the Python 3.13 rebuild (keystone (#27266), libftdi (#27269), nextpnr (#27271)), but they showed no Python-specific problems.

[lazka]

The "/lib/site-packages" "/Scripts" stuff should be fixed by 70f2ba8

[striezel]

The "/lib/site-packages" "/Scripts" stuff should be fixed by 70f2ba8

Magnificent! It looks like that fixed the problem with libmsym: #27268 (comment)

Edit: gdal also seems to be fixed, at least ucrt64, mingw64 and clangarm64 are already built by autobuild.

[lazka]

All done now. Thanks for fixing all those packages @MehdiChinoune @striezel

[striezel]

All done now. Thanks for fixing all those packages @MehdiChinoune @striezel

And thank you, too, @lazka. You and Mehdi fixed most of the blockers, I just happened to do some smaller fixes.

By the way, the Python 3.13 update should probably also be mentioned in the news section, because that was done for the Python 3.12 update, too.

[lazka]

3.12 was special in that it had many user visible changes, while 3.13 shouldn't change much for users. I'll try to come up with something.

[MehdiChinoune]

3.12 was special in that it had many user visible changes, while 3.13 shouldn't change much for users. I'll try to come up with something.

Free threading?, But it's not shipped mingw-w64-python

[lazka]

I meant things that affect MSYS2 users in particular.

We can look into free threading for 3.14, but not sure how a distro should handle it, it's basically a separate version of python, so we would need to build every package twice, and not every package supports it. We could just provide python alone though.

I've added a new entry now: https://www.msys2.org/news/#2026-01-10-python-313-update

[striezel]

We can look into free threading for 3.14, but not sure how a distro should handle it, it's basically a separate version of python, so we would need to build every package twice, and not every package supports it.

Python packages are already a very large part of the MSYS2 distribution. (Python 3.13 rebuild involved ca. 1060 packages, MSYS2 has ca. 3700 packages in total.) I don't think it is a good use of resources to build every Python package twice.

I've added a new entry now: https://www.msys2.org/news/#2026-01-10-python-313-update

Thanks. :)