On Thursday 24 April 2008 09:48:18 pm John Hunter wrote: > On Thu, Apr 24, 2008 at 5:03 PM, Eric Firing <[EMAIL PROTECTED]> wrote: > > Darren, > > > > It is open for discussion. Here are some factors: > > > > 1) In my experience, numpy is easy to build from source--easier than > > matplotlib. > > This is my view too -- if you rely on or can build svn mpl, I seen no > reason why you can't also rely on/build svn numpy since it is a much > easier build. If mpl builds, numpy svn is pretty much guaranteed to > build on any platform. > > If I am missing something Darren, please let me know, but in my > regular workflow, I pretty much assume I can bild svn ipython, numpy > and mpl, and hopefully scipy.
I have been developing a data acquisition and analysis program for my lab, and we are actually in the process of using it it this week and next to run experiments with our visiting scientists. I've been running matplotlib from svn for as long as I can remember and hadn't anticipated trouble. I guess I just wasn't reading the dev list closely enough since I rely on the trunk for daily use. Maybe we should consider cutting a transitional prelease at some point before additional big changes are made, so those of us who have already transitioned our code to the new codebase have a reference build we can install when we run into trouble on the trunk? ------------------------------------------------------------------------- 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
