Feature request: various scheme variants that put timestamps into a valid part to enable test-pypi uploads of different commits that may share distance but not content

[Wrzlprmft]

The no-local-version scheme is nice if you want to upload to TestPyPI since it does not accept nodes in the version. However, this makes every version in between tags the same and thus the second upload fails since the file already exists. This can be circumvented by just skipping existing files, but that prevents you from testing the entire publishing step, which the point of this.

Unless I am misunderstanding something, this would be solved with a local scheme that just includes the timestamp, but not the node.

Also see this Stack Overflow Q&A of mine.

[Wrzlprmft]

Apparently, this is not such a good idea after all, as the part of the guide that recommends always publishing to TestPyPI is under scrutiny at the moment.

[RonnyPfannschmidt]

there is a plan to make test pypi more easy by skipping local versions on main branches on CI

[RonnyPfannschmidt]

the first part of this is done via #311 in #1171 - currently the timestamp is still not used however - i'm working on fitting instruction