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
Idea: build from SDists #597
Comments
That's a great idea. Even in simpler workflows than the one suggested, it would undoubtedly simplify some CI workflows. see also: |
It is now possible to call the cibuildwheel command line and point it to a package source distribution archive tarball (sdist) instead of only a directory. Reference: pypa#597 Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
I pushed a minimally working branch that works super simply: the "package_dir" CLI argument can now be an sdist tarball and will be used to build the wheel if provided. It only works with the pip build backend (and not "build"). |
It is now possible to call the cibuildwheel command line and point it to a package source distribution archive tarball (sdist) instead of only a directory. Reference: pypa#597 Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
It is now possible to call the cibuildwheel command line and point it to a package source distribution archive tarball (sdist) instead of only a directory. Reference: pypa#597 Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
It is now possible to call the cibuildwheel command line and point it to a package source distribution archive tarball (sdist) instead of only a directory. The sdist must be a .tar.gz tarball and will be extracted in place before being built. Reference: pypa#597 Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
It is now possible to call the cibuildwheel command line and point it to a package source distribution archive tarball (sdist) instead of only a directory. The sdist must be a .tar.gz tarball and will be extracted in place before being built. Reference: pypa#597 Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
Just an idea, but how about allowing the "source dir" to be (a possibly remote?) SDist? If you separate the build into a different repository, having a way to put a SDist path, or simply require a user to download an SDist then put it in as a path would negate most of the need for "astrofrog/autowheel", which doesn't seem to be maintained. Just a thought.
The text was updated successfully, but these errors were encountered: