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

Require comments and string literals to be ASCII only.

This commit is contained in:
Martin v. Löwis 2007-05-17 15:37:31 +00:00
parent 6986d93450
commit 348b685294
1 changed files with 13 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
pep-3131.txt
View File

@ -92,14 +92,20 @@ http://www.dcl.hpi.uni-potsdam.de/home/loewis/table-331.html.
Policy Specification Policy Specification
==================== ====================
As an addition to the Python Coding style, the following policy is prescribed: As an addition to the Python Coding style, the following policy is
All identifiers in the Python standard library MUST use ASCII-only identifiers, prescribed: All identifiers in the Python standard library MUST use
and SHOULD use English words wherever feasible. 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, As an option, this specification can be applied to Python 2.x. In
ASCII-only identifiers would continue to be represented as byte string objects that case, ASCII-only identifiers would continue to be represented as
in namespace dictionaries; identifiers with non-ASCII characters would be byte string objects in namespace dictionaries; identifiers with
represented as Unicode strings. non-ASCII characters would be represented as Unicode strings.
Implementation Implementation
============== ==============