[Python-checkins] r53261 - peps/trunk/pep-0008.txt
barry.warsaw
python-checkins at python.org
Fri Jan 5 15:03:42 CET 2007
Author: barry.warsaw
Date: Fri Jan 5 15:03:42 2007
New Revision: 53261
Modified:
peps/trunk/pep-0008.txt
Log:
Updated the rules for package names and module names, clarifying the use of
underscores.
Modified: peps/trunk/pep-0008.txt
==============================================================================
--- peps/trunk/pep-0008.txt (original)
+++ peps/trunk/pep-0008.txt Fri Jan 5 15:03:42 2007
@@ -468,9 +468,12 @@
In some fonts, these characters are indistinguishable from the numerals
one and zero. When tempted to use `l', use `L' instead.
- Module Names
+ Package and Module Names
- Modules should have short, lowercase names, without underscores.
+ Modules should have short, all-lowercase names. Underscores can be used
+ in the module name if it improves readability. Python packages should
+ also have short, all-lowercase names, although the use of underscores is
+ discouraged.
Since module names are mapped to file names, and some file systems are
case insensitive and truncate long names, it is important that module
@@ -482,9 +485,6 @@
module that provides a higher level (e.g. more object oriented)
interface, the C/C++ module has a leading underscore (e.g. _socket).
- Like modules, Python packages should have short, all-lowercase names,
- without underscores.
-
Class Names
Almost without exception, class names use the CapWords convention.
More information about the Python-checkins
mailing list