|
From: Phil E. <pel...@gm...> - 2012-09-17 11:32:25
|
Sometimes, having a point of reference really helps in tracking the issue down, particularly when complimented with the very cool "bisect" tool that comes with git. In this case though, I knew where the problem came in because I have been working closely in this area recently (and it's my change which has exposed the problem). I have fixed this in the pull request, and fully expect the fix to be in the next 1.2.x release candidate. If your willing and able, you could get hold of my branch until it is merged to carry on testing the release candidate. Hope that helps, All the best, Phil On 14 September 2012 17:53, Scott Lasley <sl...@sp...> wrote: > > On Sep 14, 2012, at 5:02 AM, Phil Elson <pel...@gm...> wrote: > > > Thanks for raising this. I have simplified and opened an issue for the > bug (https://github.com/matplotlib/matplotlib/issues/1246) and will be > looking at this asap. > > > > All the best, > > > > Phil > > I don't know if this helps, but my scripts and the code snippet in my > email message work without crashing using matplotlib 1.2.x compiled from > github on July 23, 2012 and > numpy-1.8.0.dev_63cd8f3-py2.7-macosx-10.6-intel.egg on another mac running > OS X 10.8.1. > > Thank you for looking into this, > Scott |