I think I see what's happened. I accidentally committed a #define in
there when I was experimenting last week with removing deprecated Numpy
APIs. It didn't cause things to break for me, but it looks like it
could break things for more recent Numpy's. I've just gone ahead and
reverted my change. Let me know if that fixes things for you when you
get a chance.
Cheers,
Mike
On 12/04/2012 10:50 AM, Benjamin Root wrote:
On Tue, Dec 4, 2012 at 10:43 AM, Michael Droettboom <md...@stsci.edu
<mailto:md...@stsci.edu>> wrote:
It looks like we're using the "old" Numpy API there. Did you
recently update Numpy by any chance? I hadn't realised these APIs
had been turned off yet, but maybe they are in git master. In any
event, we should update these to the new APIs (NPY_UBYTE instead
of PyArray_UBYTE etc.).
Cheers,
Mike
Not since Nov. 5th (which was a fix for a bug I reported in numpy
master. So, I was using numpy 1.8.0 dev branch.
Cheers!
Ben Root
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
