Version in conda-forge CI is 0.0.0

[davidbrochart]

When installing Asphalt in the conda-forge CI, we get:

Successfully installed asphalt-0.0.0

This prevents using pip check in jupyverse's feedstock:

jupyverse-api 0.1.4 has requirement asphalt<5,>=4.11.0, but you have asphalt 0.0.0.
jupyverse-api 0.1.4 has requirement asphalt-web[fastapi]<2,>=1.1.0, but you have asphalt-web 0.0.0.
asphalt-web 0.0.0 has requirement asphalt~=4.8, but you have asphalt 0.0.0.
asphalt 0.0.0 has requirement asyncio-extras~=1.3, but you have asyncio-extras 0.0.0.

I cannot reproduce locally, but maybe there is an issue with setuptools_scm?

[agronholm]

I'm no expert in Anaconda matters, but it would appear that the build was done not from a git checkout, but an sdist?

[davidbrochart]

Yes, that's the preferred way of getting sources for Python packages on conda-forge.

[agronholm]

But setuptools_scm gets the version from git tags, so the sdist would not work properly. So either I should stop publishing sdists entirely, or find a mechanism in setuptools_scm that writes the version information in a file where setuptools could find it when installing from sdist?

[davidbrochart]

What about switching to hatch?

[agronholm]

I'm willing to entertain the idea, but this would probably require a PR because right now I have too much on my plate already with typeguard and anyio.

[davidbrochart]

No problem, maybe I'll try to do it.