[Python-Dev] Significance of informational PEPs

Andrew Kuchling akuchlin@mems-exchange.org
Thu, 18 Apr 2002 12:35:00 -0400

With Barry's approval, I've just checked in a minor change to PEP 1
that clarifies the significance of information PEPs:

diff -u -r1.31 pep-0001.txt
--- pep-0001.txt        5 Apr 2002 19:42:56 -0000       1.31
+++ pep-0001.txt        18 Apr 2002 16:26:32 -0000
@@ -35,7 +35,9 @@
     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.
+    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.

If people disagree about this view of informational PEPs as purely
advisory, please speak up now so we can discuss this issue.

(This came up because of the recently-posted PEP 272.  Some people on
the python-crypto list don't like PEP 272's interface at all, and
other people think the whole idea of a standard API for block
encryption is useless.  It seems impossible to come to consensus, so I
wanted to underscore that informational PEPs don't bind people to the
interfaces they describe.)

--amk                                                             (www.amk.ca)
I was continually connected with the whole world and never got any rest. At the
moment, I spend only a few hours weekly on the net, that's just better for me.
    -- Peter Greenaway, in an interview in _Page_, May 1999