You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One practical problem with the current versioning scheme is that we can't correctly version the dataclasses stub. Current upstream version is 0.8. If we use 0.8 as version, the tests try to install dataclasses==0.8.*, which doesn't work. Similar problems would exist with calver or other exotic versioning schemes.
Currently, the tests try to install f"{distribution}=={version}.*. I would suggest that we allow standard Python version range specifiers in the version field and change most existing versions to use e.g. "5.3.*". The tests would then be changed to simply install f"{distribution}=={version}". This would give us more flexibility.
Activity
srittau commentedon Sep 30, 2021
To clarify: We allow two forms:
x.y.*(the standard, any number of components) - will install the latestx.yversion in tests and gets uploaded as versionx.y.serial.x.y(any number of components) - will install exactly that version in tests and gets uploaded as versionx.y.serial.Accept plain versions or versions ending in ".*"
Accept plain versions or versions ending in ".*" (#29)
Allow third-party versions to end in asterisk
Allow third-party versions to end in asterisk (#6129)