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
wheel from sdist leads to nuisance error messages in backend #742
Comments
Perhaps there's something that should be added to the build infrastructure to let the backends (and their plugins) know that it's working from an sdist, so it can make assumptions about the source code. |
This is something that's come up a few times recently. My first question would be, what does it mean to be "working from a sdist"?
If we only want (1) to count as "building from the sdist", then maybe we could add a new flag to the I don't see any way of detecting (2), and more specifically, I see no way of distinguishing (2) and (3). Unfortunately, because of (3), we can't reasonably rely on anything in the source directory to mark it as a sdist - checking for |
Note the opening comment here says "setuptools_scm was complaining" but let's be clear what the message is:
It is unnerving as a user to see that ERROR message reported. I spent ages trying to track down what I was doing wrong until I discovered this bug which now refers to here. |
i consider this particular issue a setuptools problem - other build tools cache file details in the sdist (like hatch) |
In pypa/setuptools_scm#997, I observed that setuptools_scm was complaining about not being able to discover files when building from a git repo. As it turns out, the issue occurred when the pep517 build infrastructure was building a wheel from the sdist (so git metadata wouldn't be expected).
Originally posted by @jaraco in pypa/setuptools_scm#997 (comment)
The text was updated successfully, but these errors were encountered: