Changes between Version 4 and Version 5 of CodingStandards


Ignore:
Timestamp:
2009-05-19T19:24:14Z (15 years ago)
Author:
zooko
Comment:

go back to instructing people use alllowercasenames for modules, even though in a couple of cases (e.g. check_results.py) we use underscores for clarity.

Legend:

Unmodified
Added
Removed
Modified

  • CodingStandards

    v4 v5  
    1010=== naming and layout ===
    1111
    12  * Use {{{underscore_separated_names}}} for functions, {{{CamelCapNames}}} for classes, {{{all_lower_case_names}}} for modules, and {{{ALL_CAPS_NAMES}}} for constants. Use all lower-case variable names (e.g. {{{variable_name}}} or {{{variablename}}}). Prepend a leading underscore to private names.
     12 * Use {{{underscore_separated_names}}} for functions, {{{CamelCapNames}}} for classes, {{{alllowercasenames}}} for modules, and {{{ALL_CAPS_NAMES}}} for constants. Use all lower-case variable names (e.g. {{{variable_name}}} or {{{variablename}}}). Prepend a leading underscore to private names.
    1313 * Put parenthesis around tuples if it helps make the code more readable, leave them off it not.
    1414