On Sat, Apr 12, 2008 at 2:19 PM, Eric Firing <[EMAIL PROTECTED]> wrote: > > referring to: > > http://news.gmane.org/find-root.php?message_id=%3cc7009a550804100055g6388b20ej520e85d8e679a55%40mail.gmail.com%3e > > There was a slightly jumbled set of threads on Numpy-discussion that > included a discussion of standardizing imports, like this: > > import numpy as np > import scipy as sp > > and then this was added, as something else that had been agreed at the > same sprint: > > import pylab as plt > > I think this is a mistake, and it should have been > > import matplotlib.pyplot as plt
This is what we agreed to (import matplotlib.pyplot as plt) during the numpy sprint (I was on google chat remotely but participated in the discussion). I agree that pylab as plt would just add to the confusion. We agreed on promoting (and I currently use) import numpy as np import scipy as sp import matplotlib.pyplot as plt JDH ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
