Mercurial > pylearn

changeset 1075:d422f726c156

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
coding_style: Discussion and one more point to think about
author Olivier Delalleau <delallea@iro>
date Fri, 10 Sep 2010 11:42:48 -0400
parents ee7f34fc98fe
children 20a1af112a75
files doc/v2_planning/coding_style.txt
diffstat 1 files changed, 9 insertions(+), 0 deletions(-) [+]
line wrap: on
line diff
--- a/doc/v2_planning/coding_style.txt	Fri Sep 10 11:38:40 2010 -0400
+++ b/doc/v2_planning/coding_style.txt	Fri Sep 10 11:42:48 2010 -0400
@@ -97,6 +97,9 @@
             few typical examples (and the same happens with multi-lines lists)
 	  (Fred: I would do 2 or 3, but not 1. I find it more redable when the
 	         indent is broken after a paranthesis then at any point.
+      OD: After thinking about it, I agreee as well. My recommendation would
+          be to go with 2 when it can fit on two lines, and 3 otherwise. Same
+          with lists.
 
     * From PEP 257: The BDFL [3] recommends inserting a blank line between the
       last paragraph in a multi-line docstring and its closing quotes, placing
@@ -287,3 +290,9 @@
         raise MyException(args)
       where MyException inherits from Exception.
 
+Mercurial commits
+-----------------
+
+   * How to write good commit messages?
+   * Standardize the merge commit text (what is the message from fetch?)
+