-
-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't get proper version from sdist after version 7.0 #735
Comments
Related #727 |
This was referenced Jun 27, 2022
Ah looks like that fix hasn't been released yet. This looks like it is fixed when I install from github and run the command line version:
And it left the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My projects have been using setuptools-scm for some time now and have recently started breaking for users installing the sdist
.tar.gz
now thatsetuptools-scm
7.x is getting installed. Setuptools-scm seems to be overwriting the producedsatpy/version.py
when the wheel is built from the sdist duringpip install
. The wheel ends up with a version of 0.0 in the filename while the metadata in the sdist has 0.36.0. We usesetuptools_scm_git_archive
to pull the information from git tags.Here is how I'm reproducing it:
That's the base environment. Our package has a lot of C-based dependencies so it is easier to install from conda. If we download the most recent version from PyPI and build a wheel from it...
At first I thought it might be because of the hacky workaround we're using from #190 in our
setup.py
:but even if I remove that. commit the change, generate an sdist, untar the sdist, and run
python -m build -w .
for it I still get a wheel version of 0.0.If I force the version of
setuptools_scm
in mypyproject.toml
to 6.4.2 (the version before 7.x) then it works fine.Any ideas what I'm missing?
The text was updated successfully, but these errors were encountered: