[Python-checkins] peps: Get rid of the `Technical' PEP category. PEPs are either Standards

georg.brandl python-checkins at python.org
Wed Mar 23 21:25:53 CET 2011


http://hg.python.org/peps/rev/8a0e9b1e8d4a
changeset:   128:8a0e9b1e8d4a
user:        Barry Warsaw <barry at python.org>
date:        Wed Aug 23 05:04:42 2000 +0000
summary:
  Get rid of the `Technical' PEP category.  PEPs are either Standards
Track or Informational.

files:
  pep-0001.txt |  12 +++++-------
  1 files changed, 5 insertions(+), 7 deletions(-)


diff --git a/pep-0001.txt b/pep-0001.txt
--- a/pep-0001.txt
+++ b/pep-0001.txt
@@ -30,13 +30,11 @@
 
 Kinds of PEPs
 
-    There are three kinds of PEPs.  A standards track PEP describes a
-    new feature 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.  A technical
-    PEP describes a new implementation or other internal modification
-    that doesn't directly expose new features to the Python
-    programmer.
+    There are two kinds of PEPs.  A standards track PEP describes a
+    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.
 
 
 PEP Workflow

-- 
Repository URL: http://hg.python.org/peps


More information about the Python-checkins mailing list