[Docs] Clarify setup.cfg-only Package Release Tagging

[markgras]

Summary

Reading the current setuptools v58.2.0 documentation, it is unclear to me how to tag setup.cfg-only package releases. This page mentions that you can add tag settings to your setup.cfg file. However, this page does not mention this at all.

My specific goal in reading the documentation was to learn how to tag a setup.cfg-only package with a custom build tag, in the style of --tag-build=STRING.

OS / Environment

No response

Additional Information

This documentation change better helps developers move toward a setup.cfg-only setuptools future.

Code of Conduct

• I agree to follow the PSF Code of Conduct

[abravalheri]

Hi @markgras, thank you very much for opening this issue.

Any chance this is related to #2491? (i.e. are you using python -m build?)

[markgras]

Not necessarily. This issue is that the documentation doesn't tell a user how to tag setup.cfg-only packages. If passing tags to python -m build is supposed to work and is the intended way that users are to tag setup.cfg-only packages, then #2491 is related. I did at one point try passing tags to python -m build and it didn't work, but it was unclear to me if I was supposed to be doing that.

[abravalheri]

Thank you very much for the clarification @markgras!
Yes, indeed this topic needs better docs, however it is likely that it will take a bit longer because there are some discussions going on.

Meanwhile, if you are using build, there is a hint on how this can be done in pypa/build#202 (comment), but I suspect you can also try borrowing a bit of setuptools' own configuration:

setuptools/setup.cfg

Lines 138 to 140 in 6092cdc

	[egg_info]
	tag_build = .post
	tag_date = 1

This is a distutils configuration, but there might be some dragons.

[markgras]

Understood. Thank you for sharing these workarounds.