Eli Schwartz looked at this and found the following: ``` If we look at Debian's import of the new version: https://salsa.debian.org/python-team/packages/python-deprecation/-/commit/37e3c16c60cbcc0587a6ccbae5abf6894b011863
We see that although it changed lots of code, it didn't change deprecation.__version__ (which setup.py uses to programmatically single-source the version). And we can also see from the upstream github repository of the PyPI package, that the version was updated in git: [briancurtin/deprecation@a740a40]( https://github.com/briancurtin/deprecation/commit/a740a4023e08cc75fe4b2890359d6265ef39c062 ) ... but only after the actual release was git tagged in: [briancurtin/deprecation@c2c1e6b]( https://github.com/briancurtin/deprecation/commit/c2c1e6b4360b0d1c4de48a61187a2173321ec7b9 ) So Debian's packaging plainly imported from github, not from PyPI, for whatever reason. And as a result, they have packaged a version that isn't quite one thing but isn't the other either. The only material difference is that the metadata is wrong... ``` Hope this additional information helps. The full discussion is at https://github.com/pypa/pip/issues/13143#issuecomment-2594438563.
