Closed jGaboardi closed 1 year ago
Welp... seems like versioneer
requires a setup.cfg
file...
I had thought this ability had been added in versioneer
(xref https://github.com/python-versioneer/python-versioneer/pull/330). But seems like I misunderstood.
May have missed a step.
A side note - with the packages built from scratch, I've recently used setuptools_scm
instead of versioneer. From a user perspective it works the same as it pulls tags from git but it has very little hassle around. Just this and this. The rest is magic. You don't need any other files like with versioneer and works with pyproject.toml.
@martinfleis So we'll probably want to stick with versioneer
across the ecosystem (at least for now), right? If so, would you say the path of least resistance is adding back a minimal setup.cfg
with only versioneer
info it? (Though not ideal...).
Yeah, I am just not happy that we're stuck with having all setup.py
because of versioneer and GitHub, setup.cfg
and pyproject.toml
... it contradicts all the efforts to have it all in one place.
Yeah, I am just not happy that we're stuck with having all
setup.py
because of versioneer and GitHub,setup.cfg
andpyproject.toml
... it contradicts all the efforts to have it all in one place.
Exactly...
Ah, good. At least something :)
You will also need to include https://github.com/geopandas/geopandas/pull/2695
I'll go ahead and update pypa/gh-action-pypi-publish@master
to pypa/gh-action-pypi-publish@release/v1
here.
This PR is a first attempt at implementing a
versioneer
update action (xref https://github.com/geopandas/geopandas/pull/2638, etc.) due to release action failure (in turn caused by #690).