Re: [matplotlib-devel] How to decouple non-GUI stuff from the GUI?

2010-12-14 Thread Christopher Barker
On 12/14/10 11:25 PM, Ludwig Schwardt wrote: > - The only GUI backends worth building on Mac OS X are TkAgg and the > native macosx one, in my humble opinion. wx works just fine on OS-X, though I'm pretty sure it's no longer a build-time dependency (no compiled code) > - I have been successfully

Re: [matplotlib-devel] How to decouple non-GUI stuff from the GUI?

2010-12-14 Thread Ludwig Schwardt
Hi, Weighing in on the Mac build issue: - The only GUI backends worth building on Mac OS X are TkAgg and the native macosx one, in my humble opinion. Sticking to them will prevent the kind of pain Kynn described. These backends are autodetected by default during the build process and you only lan

Re: [matplotlib-devel] memory leak in canvas.draw() in TkAgg

2010-12-14 Thread Benjamin Root
On Tue, Dec 14, 2010 at 5:26 PM, Russell Owen wrote: > On Dec 14, 2010, at 2:38 PM, Benjamin Root wrote: > > On Tue, Dec 14, 2010 at 4:22 PM, Benjamin Root wrote: > >> >> >> On Tue, Dec 14, 2010 at 4:06 PM, Russell Owen wrote: >> >>> On Dec 14, 2010, at 1:50 PM, Benjamin Root wrote: >>> >>> On

Re: [matplotlib-devel] memory leak in canvas.draw() in TkAgg

2010-12-14 Thread Benjamin Root
On Tue, Dec 14, 2010 at 4:22 PM, Benjamin Root wrote: > > > On Tue, Dec 14, 2010 at 4:06 PM, Russell Owen wrote: > >> On Dec 14, 2010, at 1:50 PM, Benjamin Root wrote: >> >> On Tue, Dec 14, 2010 at 3:18 PM, Russell E. Owen wrote: >> >>> I tried the test script on linux using matplotlib svn trun

Re: [matplotlib-devel] memory leak in canvas.draw() in TkAgg

2010-12-14 Thread Russell Owen
On Dec 14, 2010, at 1:50 PM, Benjamin Root wrote: On Tue, Dec 14, 2010 at 3:18 PM, Russell E. Owen wrote: I tried the test script on linux using matplotlib svn trunk rev8840 (which appears to include your patch) and found a leak that starts out small but gets systematically larger. This is with

Re: [matplotlib-devel] memory leak in canvas.draw() in TkAgg

2010-12-14 Thread Russell Owen
On Dec 14, 2010, at 2:38 PM, Benjamin Root wrote: On Tue, Dec 14, 2010 at 4:22 PM, Benjamin Root wrote: On Tue, Dec 14, 2010 at 4:06 PM, Russell Owen wrote: On Dec 14, 2010, at 1:50 PM, Benjamin Root wrote: On Tue, Dec 14, 2010 at 3:18 PM, Russell E. Owen wrote: I tried the test scrip

Re: [matplotlib-devel] memory leak in canvas.draw() in TkAgg

2010-12-14 Thread Benjamin Root
On Tue, Dec 14, 2010 at 4:06 PM, Russell Owen wrote: > On Dec 14, 2010, at 1:50 PM, Benjamin Root wrote: > > On Tue, Dec 14, 2010 at 3:18 PM, Russell E. Owen wrote: > >> I tried the test script on linux using matplotlib svn trunk rev8840 >> (which appears to include your patch) and found a leak

Re: [matplotlib-devel] memory leak in canvas.draw() in TkAgg

2010-12-14 Thread Benjamin Root
On Tue, Dec 14, 2010 at 3:18 PM, Russell E. Owen wrote: > I tried the test script on linux using matplotlib svn trunk rev8840 > (which appears to include your patch) and found a leak that starts out > small but gets systematically larger. This is with Python 2.6.5 and > Tkinter built against Tcl/

Re: [matplotlib-devel] memory leak in canvas.draw() in TkAgg

2010-12-14 Thread Russell E. Owen
I tried the test script on linux using matplotlib svn trunk rev8840 (which appears to include your patch) and found a leak that starts out small but gets systematically larger. This is with Python 2.6.5 and Tkinter built against Tcl/Tk 8.4.13. Is anyone else seeing this? time rss memorym

Re: [matplotlib-devel] memory leak in canvas.draw() in TkAgg

2010-12-14 Thread Russell E. Owen
I already posted results using the svn trunk plus the svn trunk with your patch (as well as the 1.0.0 release). I updated them today with a few more options (such as your patch without setting the x limit -- it didn't make any difference) and letting them run longer. Here they are. All are from

Re: [matplotlib-devel] memory leak in canvas.draw() in TkAgg

2010-12-14 Thread Michael Droettboom
If you're able to try this with the 1.0.x SVN branch or the SVN trunk (plus my text patch) let me know. I am not able to reproduce any sort of memory leak with these newer versions, but I am able to with 1.0.0 as released (with or without my text patch). This is with or without the x axis lim

Re: [matplotlib-devel] Sourceforge status

2010-12-14 Thread Benjamin Root
Thanks! Ben On Tue, Dec 14, 2010 at 9:44 AM, Michael Droettboom wrote: > You need to be granted those permissions in the SourceForge admin > interface. I've just gone ahead and done so for you. > > Mike > > > On 12/13/2010 04:23 PM, Benjamin Root wrote: > > Does some other setting needs to be

Re: [matplotlib-devel] Sourceforge status

2010-12-14 Thread Michael Droettboom
You need to be granted those permissions in the SourceForge admin interface. I've just gone ahead and done so for you. Mike On 12/13/2010 04:23 PM, Benjamin Root wrote: Does some other setting needs to be made to allow me to change the status of bug reports in sourceforge? I can't close repo