-
-
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 supersedes PEP 513, PEP 571, PEP 599 #1960
Conversation
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 got no power for the PEP processes, but... LGTM!
I forgot to put this one hold. #1962 needs to go in first. |
,,, and #1962 is waiting on approval from the PEP 599 and PEP 600 authors (either on the PR itself, or in the Discourse thread raised for it).. |
c.f. Discourse thread for more details |
What's the status of this PR? |
Waiting for @takluyver to approve #1962 I'm inclined to merge both PRs if @takluyver doesn't raise any objections in the next day or two. |
Per PEP 600: ``` When this PEP is accepted, the previous manylinux PEPs will receive a final update noting that they are no longer maintained and referring to this PEP. ```
@mayeut if you take this PR out of draft mode and ping me, I'll merge it. |
@pfmoore, rebased on master and marked ready for review. |
Sigh. Looks like that triggered a couple more review requests via codeowners. I don't think I have the authority to override the requirement for those (I'm only the sponsor on this PEP). |
Per PEP 600: