matplotlib-devel Mailing List for matplotlib

Jeff,
Travis fixed the problem on Saturday (r5155). Trac doesn't seem to have 
the nice feature of sending an email to the originator of a ticket when 
it is changed or closed, and I didn't check until this morning. I 
don't know whether this fix, or any other recent fixes, or fixes yet to 
be made (addressing memory leaks that seem to have cropped up--see 
ticket 774) will get into the release.
The problem that I reported was triggered by an array created by 
scipy.io.loadmat, reading an old-format mat file created by custom code. 
 I suspect most users would never trip over it. I never did figure out 
what was different about the dtype of that array.
Eric
Jeff Whitaker wrote:
> Eric Firing wrote:
>> Jeff,
>>
>> The problem is not in basemap, it is numpy. Basemap is doing the 
>> right thing, using the astype method to ensure a copy--but that is not 
>> what the method is actually doing in this case. I filed a numpy 
>> ticket (788). I took a quick look at the numpy code but did not find 
>> anything obviously amiss.
>>
>> If this does not get solved in numpy right away, the workaround in 
>> basemap/pyproj _copytobuffer is to use npy.array(x, dtype=npy.float64, 
>> copy=True) instead of the astype method.
>>
>> Eric
> 
> Eric: Thanks a lot for tracking this down - great detective work! 
> I'll keep an eye on the ticket and if it doesn't get fixed in 1.1 I'll 
> use your suggested workaround.
> 
> -Jeff
>>
>> Eric Firing wrote:
>>> Jeff,
>>>
>>> I sent that last message a little too quickly. Now I see that pyproj 
>>> really is trying to ensure a copy--that is what the comments and 
>>> docstring say--so I will simply try to find and fix the bug, the 
>>> particular case in which a copy is not being made.
>>>
>>> Eric
>>>
>>> Eric Firing wrote:
>>>> Jeff,
>>>>
>>>> I ran into a major bug that I think results from a fairly 
>>>> deep-seated gotcha in basemap. The problem lies with the in-place 
>>>> transformation of 
>> [...]
> 
> 

I will be mostly out of touch for the next few days, but feel free to
proceed with the 0.91.3 and 0.98.beta pre-release as you all see fit
as you clear up the remaining hurdles.
Thanks,
JDH