-
Notifications
You must be signed in to change notification settings - Fork 239
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
Add note about the planned change of the manylinux default #1992
Conversation
Co-authored-by: Henry Schreiner <[email protected]>
Maybe it will be a good practice to promise that all changing manylinux images should be end of January? |
I'm afraid I don't follow your logic. What's the relevance of January? The proposal was to change the default at the end of June 2025. |
I do not know why I read June as January. |
Oh, I see. Yeah, that's a good idea. We're often beholden to external factors too, but let's see if it works to stick to a June cadence on the next one. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fine by me, but mostly needs @mayeut's approval.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, I see. Yeah, that's a good idea. We're often beholden to external factors too, but let's see if it works to stick to a June cadence on the next one.
Indeed external factors do exist and not only for cibuildwheel.
In order for the image sizes of manylinux not to grow too much, I'll try to remove EOL ones (when they can be removed) at the time of the new Python 3.x beta.
Given the release schedule of last CPython versions, this generally happens at the beginning of May.
Co-authored-by: Matthieu Darbois <[email protected]>
As per discussion in #1772, note about the planned update of the manylinux default.