tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

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]
zooko 2009-05-19 19:24:14 +00:00
parent dbead24c8b
commit 159c9fb8c9
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
CodingStandards.md

@ -9,7 +9,7 @@ Tahoe requires Python v2.4.2 or greater. No effort should be made to offer compa
### naming and layout ### 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. * Put parenthesis around tuples if it helps make the code more readable, leave them off it not.
### comments, idioms, miscellany, license ### comments, idioms, miscellany, license