Skip to content

PEP 1: List the PPC as authorized PEP sponsors along with anyone they appoint #5196

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.

Sign up for GitHub

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

Merged
brettcannon merged 2 commits into from
Oct 26, 2026
+18 −15
Merged

PEP 1: List the PPC as authorized PEP sponsors along with anyone they appoint #5196

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
10ba01a
PEP 1: List the PPC as authorized PEP sponsors along with anyone they…
brettcannon Oct 26, 2026
0539e48
Apply batched suggestions from code review
brettcannon Oct 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 18 additions & 15 deletions peps/pep-0001.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -160,21 +160,24 @@ initial concerns about the proposal.
Submitting a PEP
----------------
Comment thread
brettcannon marked this conversation as resolved.

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:

- 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`)
- 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. 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
Expand Down
Loading