Changes between Version 13 and Version 14 of TracDev/CodingStyle

Timestamp:

Dec 30, 2010, 5:03:33 PM (13 years ago)

Author:

anonymous

Comment:

minor spelling changes

TracDev/CodingStyle

@@ -3 +3 @@
 Executive summary: we'll usually frown on patches that 
  - have long lines
- - have multiple statement per lines
+ - have multiple statements per line
  - break the naming conventions
-because this immediately tell us the patch author hasn't tried to follow our coding conventions. On the opposite, a patch that follows the conventions detailed below tell us that the patch author has made some efforts, therefore the patch itself is much more likely to be a [[TracDev/SubmittingPatches#Whatisagoodpatch|good patch]] and has better chances to get the attention it deserves...
+because this immediately tell us the patch author hasn't tried to follow our coding conventions. On the other hand, a patch that follows the conventions detailed below tells us that the patch author has made some effort, therefore the patch itself is much more likely to be a [[TracDev/SubmittingPatches#Whatisagoodpatch|good patch]] and has a better chance to get the attention it deserves...
 
 
 Like most Python projects, we try to adhere to [pep:0008 PEP 8 (Style Guide for Python Code)] and [pep:0257 PEP 257 (Docstring Conventions)]. Be sure to read those documents if you intend to contribute code to Trac.
 
-Note that there could be that some of the current Trac code violates a couple of the rules stated below. We are always in the process of refactoring the offending modules so that all code uses the same conventions, though it's much better now than it used to be.
+Note that some of the current Trac code could violate a couple of the rules stated below. We are always in the process of refactoring the offending modules so that all code uses the same conventions, though it's much better now than it used to be.
 
 == Naming conventions ==