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

Ethan Furman's latest patch for Issue 19331.

This commit is contained in:
Barry Warsaw 2013-11-01 12:56:37 -04:00
parent 05d6e0dfad
commit b7879b52e9
1 changed files with 14 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
pep-0008.txt
View File

@ -580,6 +580,12 @@ the currently recommended naming standards. New modules and packages
standards, but where an existing library has a different style,
internal consistency is preferred.
Overriding Principle
--------------------
Names that are visible to the user as public parts of the API should
follow conventions that reflect usage rather than implementation.
Descriptive: Naming Styles
--------------------------
@ -676,8 +682,14 @@ interface, the C/C++ module has a leading underscore
Class Names
~~~~~~~~~~~
Almost without exception, class names use the CapWords convention.
Classes for internal use have a leading underscore in addition.
Class names should normally use the CapWords convention.
The naming convention for functions may be used instead in cases where
the interface is documented and used primarily as a callable.
Note that there is a separate convention for builtin names: most builtin
names are single words (or two words run together), with the CapWords
convention used only for exception names and builtin constants.
Exception Names
~~~~~~~~~~~~~~~