[Python-checkins] CVS: python/nondist/peps pep-0008.txt,1.2,1.3

2001年7月05日 13:38:13 -0700

Update of /cvsroot/python/python/nondist/peps
In directory usw-pr-cvs1:/tmp/cvs-serv11303
Modified Files:
	pep-0008.txt 
Log Message:
Make the section on consistency a separate section, as in the
original. Close an unmatched parenthesis at the very end.
Index: pep-0008.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0008.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -r1.2 -r1.3
*** pep-0008.txt	2001年07月05日 18:56:34	1.2
--- pep-0008.txt	2001年07月05日 20:38:11	1.3
***************
*** 17,23 ****
 guidelines for the C code in the C implementation of Python[1].

! Note, rules are there to be broken. Two good reasons to break a
! particular rule:

 (1) When applying the rule would make the code less readable, even
 for someone who is used to reading code that follows the rules.
--- 17,38 ----
 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]. This PEP inherits that essay's incompleteness.
! 
! 
! A Foolish Consistency is the Hobgoblin of Little Minds
! 
! A style guide is about consistency. Consistency with this style
! guide is important. Consistency within a project is more
! important. Consistency within one module or function is most
! important.
! 
! But most importantly: know when to be inconsistent -- sometimes
! the style guide just doesn't apply. When in doubt, use your best
! judgement. Look at other examples and decide what looks best. And
! don't hesitate to ask!

+ Two good reasons to break a particular rule:
+ 
 (1) When applying the rule would make the code less readable, even
 for someone who is used to reading code that follows the rules.
***************
*** 27,33 ****
 opportunity to clean up someone else's mess (in true XP style).

- This document was adapted from Guido's original Python Style
- Guide essay[2]. This PEP inherits that essay's incompleteness.
- 

 Code lay-out
--- 42,45 ----
***************
*** 378,382 ****
 that only the current class accesses an attribute. (But realize
 that Python contains enough loopholes so that an insistent user
! could gain access nevertheless, e.g. via the __dict__ attribute.

--- 390,394 ----
 that only the current class accesses an attribute. (But realize
 that Python contains enough loopholes so that an insistent user
! could gain access nevertheless, e.g. via the __dict__ attribute.)