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

#16325: remove outdated link and rephrase paragraph accordingly.

This commit is contained in:
Ezio Melotti 2012-10-28 00:33:29 +03:00
parent f1535d9c8c
commit 7c098c5c15
1 changed files with 6 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
pep-0008.txt
View File

@ -19,11 +19,9 @@ the standard library in the main Python distribution. Please see the
companion informational PEP describing style guidelines for the C code
in the C implementation of Python [1]_.
This document was adapted from Guido's original Python Style Guide
essay [2]_, with some additions from Barry's style guide [3]_. Where
there's conflict, Guido's style rules for the purposes of this PEP.
This PEP may still be incomplete (in fact, it may never be finished
<wink>).
This document and PEP 257 (Docstring Conventions) were adapted from
Guido's original Python Style Guide essay, with some additions from
Barry's style guide [2]_.
A Foolish Consistency is the Hobgoblin of Little Minds
@ -496,7 +494,7 @@ The following naming styles are commonly distinguished:
- ``UPPERCASE``
- ``UPPER_CASE_WITH_UNDERSCORES``
- ``CapitalizedWords`` (or CapWords, or CamelCase -- so named because
of the bumpy look of its letters [4]_). This is also sometimes known
of the bumpy look of its letters [3]_). This is also sometimes known
as StudlyCaps.
Note: When using abbreviations in CapWords, capitalize all the
@ -963,12 +961,10 @@ References
.. [1] PEP 7, Style Guide for C Code, van Rossum
.. [2] http://www.python.org/doc/essays/styleguide.html
.. [3] Barry's GNU Mailman style guide
.. [2] Barry's GNU Mailman style guide
http://barry.warsaw.us/software/STYLEGUIDE.txt
.. [4] http://www.wikipedia.com/wiki/CamelCase
.. [3] http://www.wikipedia.com/wiki/CamelCase
Copyright