-
Notifications
You must be signed in to change notification settings - Fork 1k
Description
I was just pointed to https://github.com/gcovr/gcovr/actions/runs/16126694419/job/45507427524#step:10:210 with an explanation that "upload failed because of the development version", which I knew was incorrect.
It was due to the local version specifier that PEP 440 forbids.
The error message states that but doesn't mention PEP 440 or a place where it's defined:
400 The use of local versions in
<Version('8.4.dev26+g5f7e08fb2')> is not allowed. See
https://packaging.python.org/specifications/core-metadata for more
information.
The URL in the message points to the generic core packaging metadata web page that has no mention of PEP 440 or versioning limitations. The version provided does comply with the metadata spec, and so this is clearly a source of confusion for people who wouldn't know where to look.
Looks like the error message should point to different URLs depending on the cause of rejection. Or contain other clues regarding what's happening.
For this problem, the correct link would be https://packaging.python.org/en/latest/specifications/version-specifiers/#local-version-identifiers or at least https://peps.python.org/pep-0440/#local-version-identifiers.
P.S. I also noticed that Version.__repr__()
seems to be leaking into the error message. So that's another/related area of improvement.