[Python-checkins] r55403 - peps/trunk/pep-3131.txt

martin.v.loewis python-checkins at python.org
Thu May 17 17:37:32 CEST 2007


Author: martin.v.loewis
Date: Thu May 17 17:37:31 2007
New Revision: 55403

Modified:
   peps/trunk/pep-3131.txt
Log:
Require comments and string literals to be ASCII only.


Modified: peps/trunk/pep-3131.txt
==============================================================================
--- peps/trunk/pep-3131.txt	(original)
+++ peps/trunk/pep-3131.txt	Thu May 17 17:37:31 2007
@@ -92,14 +92,20 @@
 Policy Specification
 ====================
 
-As an addition to the Python Coding style, the following policy is prescribed:
-All identifiers in the Python standard library MUST use ASCII-only identifiers,
-and SHOULD use English words wherever feasible.
-
-As an option, this specification can be applied to Python 2.x.  In that case,
-ASCII-only identifiers would continue to be represented as byte string objects
-in namespace dictionaries; identifiers with non-ASCII characters would be
-represented as Unicode strings.
+As an addition to the Python Coding style, the following policy is
+prescribed: All identifiers in the Python standard library MUST use
+ASCII-only identifiers, and SHOULD use English words wherever feasible
+(in many cases, abbreviations and technical terms are used which
+aren't English). In addition, string literals and comments must also
+be in ASCII. The only exceptions are (a) test cases testing the
+non-ASCII features, and (b) names of authors. Authors whose names are
+not based on the latin alphabet MUST provide a latin transliteration
+of their names.
+
+As an option, this specification can be applied to Python 2.x.  In
+that case, ASCII-only identifiers would continue to be represented as
+byte string objects in namespace dictionaries; identifiers with
+non-ASCII characters would be represented as Unicode strings.
 
 Implementation
 ==============


More information about the Python-checkins mailing list