From 10ba01a01940803c18f13754a0e169813f66da1e Mon Sep 17 00:00:00 2001 From: Brett Cannon Date: Mon, 26 Oct 2026 16:54:32 +0000 Subject: [PATCH 1/2] PEP 1: List the PPC as authorized PEP sponsors along with anyone they appoint --- peps/pep-0001.rst | 33 ++++++++++++++++++--------------- 1 file changed, 18 insertions(+), 15 deletions(-) diff --git a/peps/pep-0001.rst b/peps/pep-0001.rst index e90d7ff8787..42615d88426 100644 --- a/peps/pep-0001.rst +++ b/peps/pep-0001.rst @@ -160,21 +160,24 @@ initial concerns about the proposal. Submitting a PEP ---------------- -Following the above initial discussion, the workflow varies based on whether -any of the PEP's co-authors are core developers. If one or more of the PEP's -co-authors are core developers, they are responsible for following the process -outlined below. Otherwise (i.e. none of the co-authors are core developers), -then the PEP author(s) will need to find a sponsor for the PEP. - -Ideally, a core developer sponsor is identified, but non-core sponsors may also -be selected with the approval of the Steering Council. Members of the GitHub -"PEP editors" team and members of the Typing Council (:pep:`729`) are -pre-approved to be sponsors. The sponsor's job is to -provide guidance to the PEP author to help them through the logistics of the -PEP process (somewhat acting like a mentor). Being a sponsor does **not** -disqualify that person from becoming a co-author or PEP-Delegate later on (but -not both). The sponsor of a PEP is recorded in the "Sponsor:" field of the -header. +Following the above initial discussion, a *sponsor* must be found for the PEP. +If one or more of the PEP's co-authors qualify as a sponsor, they are responsible +for following the process outlined below. Otherwise (i.e. none of the co-authors +are sponsors), the PEP author(s) will need to find a sponsor for the PEP. + +People approved to be PEP sponsors are: + +- Python core developers +- Members of the GitHub "PEP editors" team +- Members of the Typing Council (:pep:`729`) +- Members of the Packaging Council (:pep:`772`) +- People appointed by the Steering or Packaging Councils + +The sponsor's job is to provide guidance to the PEP author to help them through +the logistics of the PEP process (somewhat acting like a mentor). Being a +sponsor does **not** disqualify that person from becoming a co-author or +PEP-Delegate later on (but not both). The sponsor of a PEP is recorded in the +"Sponsor:" field of the header. Once the sponsor or the core developer(s) co-authoring the PEP deem the PEP ready for submission, the proposal should be submitted as a draft PEP via a From 0539e487d968b6792699042cbc84ad425bed0eac Mon Sep 17 00:00:00 2001 From: Brett Cannon Date: Mon, 26 Oct 2026 12:35:31 -0700 Subject: [PATCH 2/2] Apply batched suggestions from code review Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> Co-authored-by: Barry Warsaw --- peps/pep-0001.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/peps/pep-0001.rst b/peps/pep-0001.rst index 42615d88426..5eba57d776b 100644 --- a/peps/pep-0001.rst +++ b/peps/pep-0001.rst @@ -167,7 +167,7 @@ are sponsors), the PEP author(s) will need to find a sponsor for the PEP. People approved to be PEP sponsors are: -- Python core developers +- Members of the Python core team - Members of the GitHub "PEP editors" team - Members of the Typing Council (:pep:`729`) - Members of the Packaging Council (:pep:`772`) @@ -176,7 +176,7 @@ People approved to be PEP sponsors are: The sponsor's job is to provide guidance to the PEP author to help them through the logistics of the PEP process (somewhat acting like a mentor). Being a sponsor does **not** disqualify that person from becoming a co-author or -PEP-Delegate later on (but not both). The sponsor of a PEP is recorded in the +PEP-Delegate later on. The sponsor of a PEP is recorded in the "Sponsor:" field of the header. Once the sponsor or the core developer(s) co-authoring the PEP deem the PEP