On 7/9/07, Michael Droettboom <[EMAIL PROTECTED]> wrote: > > I am about to update the memory leak question in the FAQ, but I thought I'd > run it by the list first. I removed language that talked about much earlier > releases of mpl, and the paragraph about leaks in older versions of Numeric > and numarray. It seems like we should recommend numpy when the user > experiences problems with Numeric or numarray, but I wanted to confirm that > before adding a paragraph to that effect.
vis-a-vis numpy, since we are dropping support entirely for Numeric and numarray, you can definitely recommend numoy :-) The looks very good, but I would also point them to memleak_hawaii or something to diagnose a pure image backend. Many times it is simply the user script that is failing (they fail to properly close a figure they have opened) so the FAQ should at least point them to an image generation script that is written correctly. The GUI leaks are are current problem, but they are 2nd order. We first need to make sure the pure MPL part is not leaking (it isn't currently, but it might one day if we screw something up in extension code) and once we've verified that, we can isolate the GUI leaks. Thanks, JDH ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
