I plan to update python-typeguard from 2.12.3 to 4.0.0[1] in Rawhide.
Version 3 of typeguard included a number of breaking changes[2], and
4.0.0 included a few as well[3].
Directly-dependent package compatibility with version 4.0.0 is as follows:
- python-nptyping is compatible
- python-signature-dispatch will be compatible with a concurrent
update from 1.0.0 to 1.0.1[4]
- python-stack-data has dropped the dependency in Rawhide
- python-TestSlide is incompatible, but (1) the package already
FTBFS in F38 and Rawhide, and (2) I opened PR’s to fix the existing
FTBFS[5] and typeguard 4 compatibility[6] about a month ago. The
maintainers can easily fix the incompatibility whenever they want to
address the existing FTBFS.
While the Updates Policy prescribes one week’s notice for
API-incompatible updates like this[7], the intent of that rule is to
avoid breaking packages without notice. In this case, python-typeguard
already FTBFS in Rawhide since python-typing-extensions was updated from
4.5.0 to 4.6.2, and this incompatible update is required to fix that. If
the package is not updated, python-typeguard and everything that
directly or indirectly depends on it will fail in the Python 3.12 mass
rebuild.
I have therefore asked FESCo for permission to update immediately rather
than waiting out the usual one-week notice period.[8]
[1]
https://src.fedoraproject.org/rpms/python-typeguard/pull-request/3
[2]
https://github.com/agronholm/typeguard/blob/3.0.0/docs/versionhistory.rst...
[3]
https://github.com/agronholm/typeguard/blob/4.0.0/docs/versionhistory.rst...
[4]
https://src.fedoraproject.org/rpms/python-signature-dispatch/pull-request/1
[5]
https://src.fedoraproject.org/rpms/python-TestSlide/pull-request/1
[6]
https://src.fedoraproject.org/rpms/python-TestSlide/pull-request/2
[7]
https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#_rawhide
[8]
https://pagure.io/fesco/issue/3014