iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 8013: Clarify that a core developer is required to submit PEPs for approval (#782)

This commit is contained in:
Steve Dower 2018-09-18 11:08:56 -07:00 committed by GitHub
parent 92f323c079
commit 5fc091d945
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
pep-8013.rst
View File

@ -91,7 +91,13 @@ that are expected.
GUIDO only pronounces on PEPs submitted to python-committers. There is GUIDO only pronounces on PEPs submitted to python-committers. There is
no expectation that GUIDO follows or participates on any other mailing no expectation that GUIDO follows or participates on any other mailing
lists. lists. (Note that this implies that only core developers may submit
PEPs. Non-core developers may write and discuss proposals on other
mailing lists, but without a core developer willing to support the
proposal by requesting pronouncement, it cannot proceed to acceptance.
This is essentially the same as the current system, but is made
explicit here to ensure that members of GUIDO are not expected to deal
with proposals that are not supported by at least one core developer.)
GUIDO may not delegate authority to individuals who have not been GUIDO may not delegate authority to individuals who have not been
elected by the core developer team. (One relevant case here is that elected by the core developer team. (One relevant case here is that