[matplotlib-devel] master macosx backend broken?

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] master macosx backend broken?

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?

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?

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

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

On 2013/09/17 8:09 PM, Matt Terry wrote: > 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 pl

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

On 2013/09/17 4:14 PM, Damon McDougall wrote: > 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

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

Is it time to have the discussion about dropping the MacOS backend? I know an incredible amount of top quality developer time has gone into it, but in truth it is not up to the *Agg backends and without another massive amount of work, never will be. Not to mention the drag that having YAB (yet ano

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

I think an objective comparison of features and performance between Agg and macosx would be a helpful place to start the discussion, just so we know what we're talking about here. I seem to recall one of Michiel de Hoon's original motivations was performance, perhaps related to hardware render

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

On Wed, Sep 18, 2013 at 5:30 AM, Phil Elson wrote: > Is it time to have the discussion about dropping the MacOS backend? > > I know an incredible amount of top quality developer time has gone into > it, but in truth it is not up to the *Agg backends and without another > massive amount of work, n

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

On 09/18/2013 12:28 PM, Matt Terry wrote: On Wed, Sep 18, 2013 at 5:30 AM, Phil Elson > wrote: Is it time to have the discussion about dropping the MacOS backend? I know an incredible amount of top quality developer time has gone into it, but in truth it

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

FWIW, once getting past the error reported by Eric in 2431, I am able to reproduce this on my Mac. I'm looking into it. I suspect something in the macosx backend is getting passed a unicode string where it used to get a byte string. Mike On 09/17/2013 10:14 PM, Damon McDougall wrote: > On Tue

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

Try this. It at least gets "simple_plot.py" running again on the OS-X backend. https://github.com/matplotlib/matplotlib/pull/2433 Mike On 09/18/2013 12:42 PM, Michael Droettboom wrote: FWIW, once getting past the error reported by Eric in 2431, I am able to reproduce this on my Mac. I'm look

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

On 09/18/2013 12:33 PM, Michael Droettboom wrote: On 09/18/2013 12:28 PM, Matt Terry wrote: On Wed, Sep 18, 2013 at 5:30 AM, Phil Elson > wrote: Is it time to have the discussion about dropping the MacOS backend? I know an incredible amount of top quality d

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

Hi all, At the time when the Mac OS X backend was first introduced, its performance was significantly better than other backends, but this was due to the way its event loop is organized. Nowadays the other backends use the same event loop organization, and as far as I know currently there is no

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

Hi all, Don't get me wrong, I am not thrilled with the macosx backend, especially that can't-draw-outside-the-event-loop issue,... I don't think this is a disadvantage: The macosx backend just enforces a cleaner coding style. The other backends are more forgi

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

Hi all, Cocoaagg could solve a lot of problems, but it depends on whether pyojbc is being actively maintained. I seem to remember that that was not always the case in the past. If we do decide pyobjc, we may consider a agg-free backend that does not require any compilation. Best, -Michiel.

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

@lists.sourceforge.net Sent: Thursday, September 19, 2013 2:14 AM Subject: Re: [matplotlib-devel] master macosx backend broken? Try this.  It at least gets "simple_plot.py" running again on the OS-X backend. https://github.com/matplotlib/matplotlib/pull/2433 Mike On 09/18/2013 12:42 P

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

*Subject:* Re: [matplotlib-devel] master macosx backend broken? Try this. It at least gets "simple_plot.py" running again on the OS-X backend. https://github.com/matplotlib/matplotlib/pull/2433 Mike On 09/18/2013 12:42 PM, Michael Droettboom wrote: FWIW, once getting past the error r