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
document how/when a PR here takes it to the next step of becoming PEP in the PEP index.
who has to approve? based on what?
if we want people to try to write PEPs, they need to know how it moves along.
The text was updated successfully, but these errors were encountered:
@dstufft and I have access to create new ones directly (as does Paul Moore now), otherwise folks can follow the submission process in PEP 1.
There's also a matter of capturing the way we use the PEP process: https://mail.python.org/pipermail/distutils-sig/2015-September/026810.html
I'm now wondering if that might be better served by being captured on pypa.io rather than being a PEP.
Sorry, something went wrong.
I've aimed to cover at least the basics of this in pypa/pypa.io#12
(It's not enough to close this issue, but it's a start)
Better reference for the process update: pypa/pypa.io#11
No branches or pull requests
document how/when a PR here takes it to the next step of becoming PEP in the PEP index.
who has to approve? based on what?
if we want people to try to write PEPs, they need to know how it moves along.
The text was updated successfully, but these errors were encountered: