Fernando Perez wrote: > On 8/12/07, Eric Firing <[EMAIL PROTECTED]> wrote: >> mlab.py in svn has now been changed quite a bit:
> But if I may make a small comment, in my view MPL should simply not > contain any numerics, period (beyond that needed for plotting > functions). For the most part,m I agree with Fernando on this. However, the numpy team is making a concerted effort to have numpy be pretty straight core functionality. All the stuff in mlab will not and should not be put into numpy. However, it's a lot of useful stuff. What to do? I think it probably belongs in SciPy -- after all, SciPy is a lot of useful stuff (some domain-specific, some not) built on top of numpy. However, mlab is now in MPL, and I think Eric is doing a great job of cleaning things up, so that the mlab module it self could easily be moved somewhere else in the future. A couple points to keep in mind: Does internal MPL code rely on mlab? if so, it needs to be part of some core lib that is stable enough to be a MPL dependency. Despite what Fernando and I think, a lot of people DO want MPL to be an all-in-one plotting AND computing environment -- like Matlab. I think Scipy is what should be the complete environment, and I think it's getting close, but there are all still issues, so MPL does fill a need. -Chris ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
