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
Update default image away from manylinux2014 #1772
Comments
And also, although this is a separate issue, decide on a timeline for dropping support for |
FYI, manylinux1 and manylinux2010 were supported well past CentOS EoL, in fact manylinux1 is still receiving automated updates and is still supported in cibuildwheel (CentOS 5). 20% of systems cannot support manylinux_2_28 (https://mayeut.github.io/manylinux-timeline/), based solely on the GLIBC version (you also need a recent pip version, which might limit it further). 70% of projects still distribute manylinux2014 wheels. So while this might change, I don't think it's likely to until after the EoL deadline. (That might help it start to change). |
We could also do it conditionally, based on Python version. So for example, practically all Python 3.12 consumers support glibc 2.31 or higher. Almost all Python 3.11 consumers support 2.28 or higher. So you could end up with something like:
Of course this needs to be properly announced, and maybe some policy for instated to update those numbers. |
Hmm..! Nice idea, downside would be that it is a bit wasteful in time and bandwidth, as a default. Much of the time of a build is downloading the container, plus, some users do heavy stuff in |
a great reference here is @mayeut's manylinux timeline |
Description
CentOS 7 (on which
manylinux2014
is based) goes end-of-life in only a few months (June) - as such it's probably a good idea to look for a new default base image. Almost certainlymanylinux_2_28
.Build log
No response
CI config
No response
The text was updated successfully, but these errors were encountered: