You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building wheels for a project that has a build script, it would be very useful to be able to tag the wheels as abi3 compatible (assuming the build script outputs abi3 compatible libs).
We (Synapse) use a build script and setuptools_rust to allow us to use Rust code. In CI we use cibuildwheel to build wheels for various platforms and architectures, which can take a significant amount of time. Having to build a wheel for each cpython version unnecessarily is a significant chunk of that time.
I'm not familiar with how this is meant to work across different build systems, but as a first step it would be useful to have some way of forcing poetry to output the wheel with an abi3 tag. I think the relevant line we decide on the tag for the wheel is here.
The text was updated successfully, but these errors were encountered:
When building wheels for a project that has a build script, it would be very useful to be able to tag the wheels as abi3 compatible (assuming the build script outputs abi3 compatible libs).
We (Synapse) use a build script and
setuptools_rust
to allow us to use Rust code. In CI we usecibuildwheel
to build wheels for various platforms and architectures, which can take a significant amount of time. Having to build a wheel for each cpython version unnecessarily is a significant chunk of that time.I'm not familiar with how this is meant to work across different build systems, but as a first step it would be useful to have some way of forcing poetry to output the wheel with an
abi3
tag. I think the relevant line we decide on the tag for the wheel is here.The text was updated successfully, but these errors were encountered: