3 ms·
Probably because setupmeta seems to only supports setup.py, which this guide doesn’t use (and isn’t generally recommended for most use cases).
by amarshall 6y ago
Probably because setupmeta seems to only supports setup.py, which this guide doesn’t use (and isn’t generally recommended for most use cases).
- 1337shadow 6y agoI maintain over 50 public packages with setup.py and most of them have setupmeta, it's great and I would recommend it for all use cases.
- amarshall 6y agoSure, and that’s fine. My statement was based off https://packaging.python.org/tutorials/packaging-projects/ https://packaging.python.org/tutorials/packaging-projects/ > dynamic metadata [(setup.py)] should be used only as an escape hatch when absolutely necessary.
- 1337shadow 6y agoDynamic version numbers based on git tags are absolutely necessary to me, to ease my continuous integration practice, that's also what openstack/pbr does amongst probably other things