From f8532304b89c3437cd7b420adada4e1755d1b692 Mon Sep 17 00:00:00 2001 From: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> Date: Tue, 27 Oct 2026 11:09:55 +0200 Subject: [PATCH 1/2] PEP 1: Add 'Finding a sponsor' heading --- peps/pep-0001.rst | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/peps/pep-0001.rst b/peps/pep-0001.rst index 5eba57d776b..9f014f71762 100644 --- a/peps/pep-0001.rst +++ b/peps/pep-0001.rst @@ -157,8 +157,8 @@ PEP to make properly formatted, of high quality, and to address initial concerns about the proposal. -Submitting a PEP ----------------- +Finding a sponsor +----------------- 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 @@ -179,6 +179,9 @@ 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. +Submitting a PEP +---------------- + 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 `GitHub pull request`_. The draft must be written in PEP style as described From 9da50713467fefd328f0d57df27a0f3af3121220 Mon Sep 17 00:00:00 2001 From: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> Date: Tue, 27 Oct 2026 11:33:46 +0200 Subject: [PATCH 2/2] Whitespace Co-authored-by: Stan Ulbrych --- peps/pep-0001.rst | 1 + 1 file changed, 1 insertion(+) diff --git a/peps/pep-0001.rst b/peps/pep-0001.rst index 9f014f71762..d7ffb374709 100644 --- a/peps/pep-0001.rst +++ b/peps/pep-0001.rst @@ -179,6 +179,7 @@ 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. + Submitting a PEP ----------------