Make it possible to post multiple-releases-in-a-day

[pradyunsg]

Are folks opposed to setting up releases with the version numbers 2021.11.15.1?

Right now, we're using calver:

trove-classifiers/setup.py

Line 30 in 4e2248b

setup_requires=["calver"],

It doesn't support multiple releases on the same day, which is an issue we've hit in #80.

[Secrus]

I know this issue is quite dated, but as a side note, I would suggest dropping calver. With setuptools moving to pyproject.toml and setup.py scripts being discouraged, using calver will be anchoring the project to old standards, since (according to setuptools docs) it won't be supported in pyproject.toml. If calver is dropped, this project could also be migrated to fully use pyproject.toml metadata declaration (either via setuptools or migrating to another tool that supports it, like flit)

[pradyunsg]

setup.py scripts being discouraged

To quote https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html:

This does not mean that setuptools itself is deprecated, or that using setup.py to configure your package builds is going to be removed.

[Secrus]

@pradyunsg I meant more that the community is going in the direction of having all possible packaging data in static config like setup.cfg/pyproject.toml. I am by no means saying that setuptools is deprecated.

[hugovk]

I suggest keeping CalVer but switching from YYYY.MM.DD to YYYY.MM.micro, where micro is set to 0 for the first release of the month, then incremented for subsequent releases.

https://calver.org/#scheme

This is similar to Black and Twisted (although they use YY) and others.

https://calver.org/users.html

For example, the first release in October, let's say on the 3rd, would be 2024.10.0. The next release on the 12th would be 2024.10.1. If we have another on the 12th, it's 2024.10.2. The next on the 18th is 2024.10.3 and so on.