-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Creating pure Python wheels when using build scripts #3594
Comments
I think there are already tickets on the topic of the platform tags of the wheel. Maybe you can find some valuable info in those. |
Thank you for the comment. Indeed, it seems that I should have searched "platform tags" more thoroughly in the Issues. I found The former already has a comment about the fact that |
FWIW, I think this is still a good idea as a stop gap until there is more full featured support build scripts. Having such an option would make it easier to build with the build script when using Currently, the only way to do this is to manually exit the |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Feature Request
Is there any way to create pure Python wheels (or universal wheels) when using build scripts?
I know that build scripts are still undocumented (#2740), but if I use
pyproject.toml
likethen
poetry build
creates a platform wheel likehello-0.1.0-cp39-cp39-manylinux2014_x86_64.whl
, which makes sense when building C-extensions.But, when one wants to use
build.py
to generate some platform-independent resource files from the source (corresponding tosetup.py build_py
), platform wheels are not needed and pure Python wheels likehello-0.1.0-py3-none-any.whl
may suffice.It would be great if one could select pure Python wheels (and possibly also universal wheels) by configuring in
pyproject.toml
, for example,The text was updated successfully, but these errors were encountered: