From 6644dcee69333b1ee59a3614bddeaa9d76dc0e75 Mon Sep 17 00:00:00 2001 From: Barry Warsaw Date: Tue, 2 Apr 2002 03:20:07 +0000 Subject: [PATCH] Add a note about how PEPs should really be more focussed, and contain a single core idea. --- pep-0001.txt | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/pep-0001.txt b/pep-0001.txt index 56e09b5a6..886da6a3c 100644 --- a/pep-0001.txt +++ b/pep-0001.txt @@ -43,10 +43,16 @@ PEP Work Flow The PEP editor, Barry Warsaw , assigns numbers for each PEP and changes its status. - The PEP process begins with a new idea for Python. Each PEP must - have a champion -- someone who writes the PEP using the style and - format described below, shepherds the discussions in the - appropriate forums, and attempts to build community consensus + The PEP process begins with a new idea for Python. It is highly + recommended that a single PEP contain a single key proposal or new + idea. The more focussed the PEP, the more successfully it tends + to be. The PEP editor reserves the right to reject PEP proposals + if they appear to unfocussed or too broad. If in doubt, split + your PEP into several well-focussed ones. + + Each PEP must have a champion -- someone who writes the PEP using + the style and format described below, shepherds the discussions in + the appropriate forums, and attempts to build community consensus around the idea. The PEP champion (a.k.a. Author) should first attempt to ascertain whether the idea is PEP-able. Small enhancements or patches often don't need a PEP and can be injected