iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Change "not" -> "not necessarily" as Jeremy suggested 

Fix typo
This commit is contained in:
Andrew M. Kuchling 2002-04-18 19:19:35 +00:00
parent bf5099b6b6
commit 98315482b7
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
pep-0001.txt
View File

@ -35,9 +35,9 @@ Kinds of PEPs
new feature or implementation for Python. An informational PEP
describes a Python design issue, or provides general guidelines or
information to the Python community, but does not propose a new
feature. Informational PEPs do not represent a Python community
consensus or recommendation, so users and implementors are free to
ignore informational PEPs or follow their advice.
feature. Informational PEPs do not necessarily represent a Python
community consensus or recommendation, so users and implementors
are free to ignore informational PEPs or follow their advice.
PEP Work Flow
@ -49,7 +49,7 @@ PEP Work Flow
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
if they appear too 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