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
> [...]
--
Jeffrey S. Whitaker Phone : (303)497-6313
NOAA/OAR/CDC R/PSD1FAX : (303)497-6449
325 BroadwayBoulder, CO, USA 80305-3328
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
