[matplotlib-devel] Bug in 1.3.0: AttributeError: 'NavigationToolbar2TkAgg' object has no attribute 'draw_idle'

2013-09-17 Thread Lorenzo Di Gregorio
Hi, I've just installed matplotlib 1.3.0 and run into the following error when using the "home" button of a figure(): Exception in Tkinter callback Traceback (most recent call last): File "C:\Python27\lib\lib-tk\Tkinter.py", line 1410, in __call__ return self.func(*args) File "C:\Python27

Re: [matplotlib-devel] Bug in 1.3.0: AttributeError: 'NavigationToolbar2TkAgg' object has no attribute 'draw_idle'

2013-09-17 Thread Thomas A Caswell
This is addressed on the master branch via #2319, but the commit where the problem was introduced is not included in 1.3.0, so I am not sure what is going on. Although, it does look like the fix should be cherry picked to the 1.3.x branch. On Tue, Sep 17, 2013 at 7:02 AM, Lorenzo Di Gregorio < l

Re: [matplotlib-devel] Bug in 1.3.0: AttributeError: 'NavigationToolbar2TkAgg' object has no attribute 'draw_idle'

2013-09-17 Thread Michael Droettboom
Yes, it does appear that the fix needs to be on 1.3.x as well. I'll cherry-pick it. In the meantime, Lorenzo, you can manually include the fix here: https://github.com/matplotlib/matplotlib/pull/2319 but this will make it into the 1.3.1 release. Mike On 09/17/2013 08:36 AM, Thomas A Caswell

[matplotlib-devel] matplotlib 1.3.1

2013-09-17 Thread Michael Droettboom
I think there's enough good bug fixes on 1.3.x now to warrant a 1.3.1 release. We have 6 blocker and 12 known bugs on that branch still. I hope to devote some time to triaging and closing as many of these as I can this week, and then maybe tagging a 1.3.1 release candidate early next week. A

Re: [matplotlib-devel] matplotlib 1.3.1

2013-09-17 Thread Eric Firing
On 2013/09/17 3:03 AM, Michael Droettboom wrote: > I think there's enough good bug fixes on 1.3.x now to warrant a 1.3.1 > release. We have 6 blocker and 12 known bugs on that branch still. I > hope to devote some time to triaging and closing as many of these as I > can this week, and then maybe

[matplotlib-devel] master macosx backend broken?

2013-09-17 Thread Eric Firing
When I build mpl from master on python.org python 2.7, Mountain Lion, and try to plot anything with the macosx backend, I am now getting an Apple crash--the plot window flashes up and vanishes, and a big OS X crash report window pops up. Ipython shows "Trace/BPT trap: 5". I have never seen an

Re: [matplotlib-devel] matplotlib 1.3.1

2013-09-17 Thread Damon McDougall
On Tue, Sep 17, 2013 at 8:03 AM, Michael Droettboom wrote: > I think there's enough good bug fixes on 1.3.x now to warrant a 1.3.1 > release. We have 6 blocker and 12 known bugs on that branch still. I > hope to devote some time to triaging and closing as many of these as I > can this week, and

Re: [matplotlib-devel] master macosx backend broken?

2013-09-17 Thread Damon McDougall
On Tue, Sep 17, 2013 at 3:49 PM, Eric Firing wrote: > When I build mpl from master on python.org python 2.7, Mountain Lion, > and try to plot anything with the macosx backend, I am now getting an > Apple crash--the plot window flashes up and vanishes, and a big OS X > crash report window pops up.

Re: [matplotlib-devel] master macosx backend broken?

2013-09-17 Thread Damon McDougall
On Tue, Sep 17, 2013 at 8:55 PM, Damon McDougall wrote: > On Tue, Sep 17, 2013 at 3:49 PM, Eric Firing wrote: >> When I build mpl from master on python.org python 2.7, Mountain Lion, >> and try to plot anything with the macosx backend, I am now getting an >> Apple crash--the plot window flashes u

Re: [matplotlib-devel] master macosx backend broken?

2013-09-17 Thread Matt Terry
My mac testing hasn't picked up on this, but I don't think we have any tests that actually draw to the screen. I have noticed a i386 linking error, but haven't gotten to it. Is there an automated way to test this? Something like: Make a simple plot show() close the window after 10s. -matt On Sep