I plan to update python-typeguard from 2.12.3 to 4.0.0 in Rawhide.

This issue requests formal permission to submit the breaking update for python-typeguard in Rawhide immediately rather than waiting out the one week notice period, since waiting would cause all dependent packages to be impacted in the Python 3.12 rebuild.

Version 3 of typeguard included a number of breaking changes, and 4.0.0 included a few as well.

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
• 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 and typeguard 4 compatibility 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, 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.

Since this issue will be moot after one week, I have requested the fast-track procedure. A devel mailing list post with the above details and a link to this issue will follow promptly.