# HG changeset patch
# User David Warde-Farley <wardefar@iro.umontreal.ca>
# Date 1285946861 14400
# Node ID 879a5633bb52379a9944f74fd855b992dfdbd98a
# Parent  10113a1050ce24c25e18fcbe4ae16c9333100c11
A small addendum about the 'import A as B' moratorium.

diff -r 10113a1050ce -r 879a5633bb52 doc/v2_planning/coding_style.txt
--- a/doc/v2_planning/coding_style.txt	Tue Sep 28 16:27:21 2010 -0400
+++ b/doc/v2_planning/coding_style.txt	Fri Oct 01 11:27:41 2010 -0400
@@ -114,6 +114,10 @@
             from foo import Bar, Blah
          when imported stuff is re-used multiple times in the same file, and
          there is no ambiguity.
+     DWF: One exception I'd like to propose to the "import A as B" moratorium
+          is that we adopt the "import numpy as np" standard that's used in
+          NumPy and SciPy itself. For NumPy heavy code this really cuts down
+	  on clutter, without significant impact on readability (IMHO).
 
    * Imports should usually be on separate lines.
      OD: I would add an exception, saying it is ok to group multiple imports