Consider using the stable API when building wheels for CPython
envgap__pallets__markupsafe-175
01 / FAILURE SIGNATURE
As reported upstream
No identifying execution failure has been captured.
Not a benchmark task.
- The project already builds and runs before the fix, so there is nothing to repair.
02 / ENVIRONMENT RECIPE
- Base commit
682effc5e67750122054925a18cdc50105c3b3ff- Manifest
setup.cfg- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
pallets/markupsafe #175 · read the original issue
I noticed your tweet about having lots of wheels (thanks for the PyPy one BTW). Perhaps you could consider creating stable ABI wheels? I think if you add ``` [bdist_wheel] py-limited-api = cp34 ``` to the `setup.cfg` then `python setup.py bdist_wheel` will build something like `MarkupSafe-1.1.1-cp34-abi3-macosx_10_6_intel.whl` which any `cpython>-3.4` will support on macosx. This would save having to create a cpython-3.4, cpython3.5, ... wheels and would also mean you would future proof yourself for any new versions of cpython. You might need to adjust the CI wheel build to only build the wheel once, since the various versions of CPython will build a wheel with the same name, I think `bdist_wheel` is unhappy if a wheel already exists.
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]