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
MANIFEST.in discrepant behavior between non-scikit-build and scikit-build projects #537
Comments
@kratsg Seems that we don't actually need that in --- a/MANIFEST.in
+++ b/MANIFEST.in
@@ -3,4 +3,4 @@ graft src
include LICENSE
exclude lower-bound-requirements.txt
-global-exclude __pycache__ *.py[cod] .*
+global-exclude __pycache__ *.py[cod] and then check with
and the build using
So I might as well go and remove that in |
4 tasks
matthewfeickert
added a commit
to scikit-hep/pyhf
that referenced
this issue
May 13, 2021
* Remove global exclude of dotfiles from MANIFEST.in to avoid potential problems with build systems - c.f. scikit-build/scikit-build#537 * Use `prune **` to remove all files from the sdist - c.f. https://packaging.python.org/guides/using-manifest-in/#manifest-in-commands - "Setuptools also has undocumented support for ** matching zero or more characters including forward slash, backslash, and colon." * Manually include all "default" files for a sdist in MANIFEST.in - c.f. https://packaging.python.org/guides/using-manifest-in/#how-files-are-included-in-an-sdist * Include AUTHORS in MANIFEST.in * Add list of sdist contents to package publishing CI - Allow for easier checking of the sdist contents in CI logs
I think this might help: #402 |
matthewfeickert
added a commit
to matthewfeickert/heputils
that referenced
this issue
Aug 5, 2021
* Remove global exclude of dotfiles from MANIFEST.in to avoid potential problems with build systems - c.f. scikit-build/scikit-build#537 * Use `prune **` to remove all files from the sdist - c.f. https://packaging.python.org/guides/using-manifest-in/#manifest-in-commands - "Setuptools also has undocumented support for ** matching zero or more characters including forward slash, backslash, and colon." * Manually include all "default" files for a sdist in MANIFEST.in - c.f. https://packaging.python.org/guides/using-manifest-in/#how-files-are-included-in-an-sdist * Add list of sdist contents to package publishing CI - Allow for easier checking of the sdist contents in CI logs
matthewfeickert
added a commit
to eschanet/simplify
that referenced
this issue
Nov 9, 2021
* Remove global exclude of dotfiles from MANIFEST.in to avoid potential problems with build systems - c.f. scikit-build/scikit-build#537 * Use `prune **` to remove all files from the sdist - c.f. https://packaging.python.org/guides/using-manifest-in/#manifest-in-commands - "Setuptools also has undocumented support for ** matching zero or more characters including forward slash, backslash, and colon." * Manually include all "default" files for a sdist in MANIFEST.in - c.f. https://packaging.python.org/guides/using-manifest-in/#how-files-are-included-in-an-sdist * Add list of sdist and wheel contents to package publishing CI - Allow for easier checking of the sdist and wheel contents in CI logs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems that fundamentally, scikit-build is treating the
.*
differently than how setuptools seems to treat it. Take for instance, thisMANIFEST.in
from pyhf:If I use something similar on a scikit-build project
I find that none of the files are being picked up (because of this global-exclude at the end). However, if I tweak that last line instead to be
then it works as expected. This is not so obvious at first glance, and it would be really nice to have something like #402 in.
The text was updated successfully, but these errors were encountered: