[Scipy-svn] r5425 - branches/0.7.x

scipy-svn@scip... scipy-svn@scip...
Sat Jan 10 05:07:33 CST 2009


Author: jarrod.millman
Date: 2009-01-10 05:07:32 -0600 (Sat, 10 Jan 2009)
New Revision: 5425

Removed:
   branches/0.7.x/FORMAT_GUIDELINES.txt
Log:
Backport r5424


Deleted: branches/0.7.x/FORMAT_GUIDELINES.txt
===================================================================
--- branches/0.7.x/FORMAT_GUIDELINES.txt	2009-01-10 11:06:05 UTC (rev 5424)
+++ branches/0.7.x/FORMAT_GUIDELINES.txt	2009-01-10 11:07:32 UTC (rev 5425)
@@ -1,27 +0,0 @@
-Follow the standard Python formatting rules when writing code for SciPy.  Guido 
-describes them "here":http://www.python.org/doc/essays/styleguide.html.  A few 
-reminders follow:
-
-   o Use 4 spaces for indentation levels.  Do not use tabs as they can result 
-     in indentation confusion.  Most editors have a feature that will insert 4 
-     spaces when the tab key is hit.  Also, many editors will automatically 
-     search/replace leading tabs with 4 spaces.
-
-   o Only 80 characters on a line.
-
-   o use all lowercase function names with underscore separated words:
-
-        def set_some_value()
-
-     instead of:
-
-        def setSomeValue()
-
-
-   o use CamelCase class names:
-
-        def BaseClass()
-
-     instead of:
-
-        def base_class()



More information about the Scipy-svn mailing list