From 5591215fe096b30a54e60dba67f9505998fe0a7f Mon Sep 17 00:00:00 2001 From: David Goodger Date: Fri, 16 Jul 2004 19:27:23 +0000 Subject: [PATCH] updated --- pep-0001.txt | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/pep-0001.txt b/pep-0001.txt index c2211ed3c..e79f0d55e 100644 --- a/pep-0001.txt +++ b/pep-0001.txt @@ -59,10 +59,12 @@ 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 into the Python development -work flow with a patch submission to the SourceForge `patch manager`_ -or `feature request tracker`_. +ascertain whether the idea is PEP-able. Posting to the +comp.lang.python newsgroup (a.k.a. python-list@python.org mailing +list) is recommended. Small enhancements or patches often don't need +a PEP and can be injected into the Python development work flow with a +patch submission to the SourceForge `patch manager`_ or `feature +request tracker`_. The PEP champion then emails the PEP editor with a proposed title and a rough, but fleshed out, draft of the PEP. This