Commits

Barry Warsaw committed f335893

Make it clear that the PEP editors can only review a completed PEP for
style and consistency. The BDFL (by way of python-dev) is the final
arbiter of the PEP for its acceptance into the language.

Comments (0)

Files changed (1)

 PEP Review & Resolution
 -----------------------
 
-Once the authors have completed a PEP, they must inform the PEP editors
-that it is ready for review.  PEPs are reviewed by the BDFL and his
-chosen consultants, who may accept or reject a PEP or send it back to
-the author(s) for revision.  For a PEP that is predetermined to be
-acceptable (e.g., it is an obvious win as-is and/or its implementation
-has already been checked in) the BDFL may also initiate a PEP review,
-first notifying the PEP author(s) and giving them a chance to make
-revisions.
+Once the authors have completed a PEP, they may request a review for
+style and consistency from the PEP editors.  However, the content and
+final acceptance of the PEP must be requested of the BDFL, usually via
+an email to the python-dev mailing list.  PEPs are reviewed by the
+BDFL and his chosen consultants, who may accept or reject a PEP or
+send it back to the author(s) for revision.  For a PEP that is
+predetermined to be acceptable (e.g., it is an obvious win as-is
+and/or its implementation has already been checked in) the BDFL may
+also initiate a PEP review, first notifying the PEP author(s) and
+giving them a chance to make revisions.
 
 The final authority for PEP approval is the BDFL. However, whenever a new
 PEP is put forward, any core developer that believes they are suitably