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.
[Imported from Trac: page CodingStandards, version 5]
parent
dbead24c8b
commit
159c9fb8c9
|
@ -9,7 +9,7 @@ Tahoe requires Python v2.4.2 or greater. No effort should be made to offer compa
|
|||
|
||||
### naming and layout
|
||||
|
||||
* 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.
|
||||
* 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.
|
||||
* Put parenthesis around tuples if it helps make the code more readable, leave them off it not.
|
||||
|
||||
### comments, idioms, miscellany, license
|
||||
|
|
Loading…
Reference in a new issue