-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
PEP 600: add manylinux2014 compatibility #1962
Conversation
Not sure if/how the fact that an update was made should be reflected in the PEP given it's not Final/Active. |
Add a link to PEP 599 Add a mention to manylinux2014 aliases
612565b
to
77c5fc2
Compare
I'm not going to be able to monitor this PR or the associated discussion. Please @-ping me explicitly when the three PEP authors have confirmed they are OK with this change. |
gentle reminder: can you review this per Paul's comment. Thanks |
gentle reminder: can you review this per Paul's comment. Thanks |
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.
I'm sorry for the delay!
I think @mayeut is currently much more involved with the manylinux machinery and definitions than I am. Perhaps PEPs, like packages, should have 'authors' and 'maintainers'. 🙂
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.
(And now I got the wrong radio button...)
Thanks @takluyver! Normally PEPs don't get substantive updates after they are published, so this isn't typically a big deal. It would probably be useful to move the specification out of the PEPs, and into https://packaging.python.org/specifications/platform-compatibility-tags/. That would also mean maintenance could be handled outside of the PEP repo. |
c.f. discussion for more details