Wheel for Python 3.11 and x86_64, manylinux_2_17 becomes manylinux_2_28 - an issue?
envgap__zeromq__pyzmq-1821
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
25545d43ba8be95d27f1215c11a03ff811c92072- Manifest
pyproject.toml- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
zeromq/pyzmq #1821 · read the original issue
During `pip install pyzmq` in a Centos 7 based docker image with Python 3.10 and Python 3.11 setup respectively, pip switches from downloading a wheel to downloading a source distribution. The reason is that for Python 3.11 of the x86_64 arch specifically, the published pyzmq wheel switched from manylinux_2_17 to 2_28. Is this a constraint stemming from pyzmq, py311, or pyzmq's release automation as configured using cibuildwheel (recently https://github.com/zeromq/pyzmq/pull/1707), or something else? I tried to figure those details out myself but got stuck, so watch out - this issue can be off topic for pyzmq as a project. ### Centos 7 with Python 3.10, pip install pyzmq ```shell Collecting pyzmq>=17 Downloading pyzmq-24.0.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (1.1 MB) ```  ### Centos 7 with Python 3.11, pip install pyzmq ```shell Collecting pyzmq>=17 Downloading pyzmq-24.0.1.tar.gz (1.2 MB) ```  ## Related - https://pypi.org/project/pyzmq/25.0.0b1/#files - https://peps.python.org/pep-0599/ - https://peps.python.org/pep-0600/
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]