From 0143c34b0cd7c4049878935e9e99fe089e2470ed Mon Sep 17 00:00:00 2001
From: warner <>
Date: Sun, 17 May 2009 01:16:09 +0000
Subject: [PATCH] (tuples), allow module_name_with_underscores

[Imported from Trac: page CodingStandards, version 4]
---
 CodingStandards.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/CodingStandards.md b/CodingStandards.md
index d6a093e..9dbc61c 100644
--- a/CodingStandards.md
+++ b/CodingStandards.md
@@ -9,8 +9,8 @@ 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, `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.
- * Always put parenthesis around tuples. Write `(spam, eggs) = fetch_breakfast()` instead of `spam, eggs = fetch_breakfast()`.
+ * 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.
+ * Put parenthesis around tuples if it helps make the code more readable, leave them off it not.
 
 ### comments, idioms, miscellany, license