Closed cmutel closed 1 year ago
As used in the github action:
python -m build -s -w
The default behavior of the build backend is failing, but if we specify that we want source distribution and wheel to be built, this works fine.
* Building wheel from sdist
<- that is the reason why the build doesn't pass, unless you specify "python -m build -s -w"
I think that if we later build conda packages from the built source distributions, this issue might come up again. In that case, we might need to add the code from PR #11
According to the build documentation:
A simple, correct PEP 517 build frontend. By default, a source distribution (sdist)
is built from {srcdir} and a binary distribution (wheel) is built from the sdist. This
is recommended as it will ensure the sdist can be used to build wheels. Pass
-s/–sdist and/or -w/–wheel to build a specific distribution. If you do this, the default
behavior will be disabled, and all artifacts will be built from {srcdir} (even if you
combine -w/–wheel with -s/–sdist, the wheel will be built from {srcdir}).
Can you help me understand why we are producing sdists which then can't be used to make wheels without raising errors? Just passing -s -w
seems like avoiding instead of fixing the problem...
You're absolutely right, the default approach for build should work (invoking python -m build
).
The error is that the version doesn't end up having the "VERSION" file.
According to setuptools documentation, if we don't use setuptools_scm
, and we want a non python file to be included in the distribution, we must include it in the MANIFEST.in
branch issue-12 contains a fix for this.
version 0.1.1 has a fix for this.
I don't understand why, but when I run
I get the following error for compliance with PEP 440:
I am 99% sure this isn't a whitespace problem, I have checked multiple times. But also switching to
0.1
doesn't seem to fix it.@tngTUDOR Any ideas?