Michael Droettboom wrote:
> Jeff Whitaker wrote:
>> Michael Droettboom wrote:
>>> Actually, this is the inverse error to the other one ;) Keeping
>>> track of which APIs are "current" is proving difficult.
>>>
>>> Try r4448... Thanks for your patience.
>>>
>>> Cheers,
>>> Mike
>>
>> Mike: That
Jeff Whitaker wrote:
> Michael Droettboom wrote:
>> Actually, this is the inverse error to the other one ;) Keeping track
>> of which APIs are "current" is proving difficult.
>>
>> Try r4448... Thanks for your patience.
>>
>> Cheers,
>> Mike
>
> Mike: That did it now, thanks!
Phew!
> Now t
Michael Droettboom wrote:
> Actually, this is the inverse error to the other one ;) Keeping track
> of which APIs are "current" is proving difficult.
>
> Try r4448... Thanks for your patience.
>
> Cheers,
> Mike
Mike: That did it now, thanks! Now trying the basemap examples, I see
that very
Actually, this is the inverse error to the other one ;) Keeping track
of which APIs are "current" is proving difficult.
Try r4448... Thanks for your patience.
Cheers,
Mike
Jeff Whitaker wrote:
> Michael Droettboom wrote:
>> Sorry. Try now (r4447). I realised I have to skip even one more lev
Michael Droettboom wrote:
> Sorry. Try now (r4447). I realised I have to skip even one more level.
>
> Cheers,
> Mike
Mike: Got a bit further this time, then hit the same error in
backend_agg.cpp:
src/backend_agg.cpp: In member function 'Py::Object
RendererAgg::draw_quad_mesh(const Py::Tuple
Sorry. Try now (r4447). I realised I have to skip even one more level.
Cheers,
Mike
Jeff Whitaker wrote:
> Michael Droettboom wrote:
>> [Jeff -- I don't know why your original e-mail never got delivered to
>> me, but I was able to see it in the archive.]
>>
>> The problem arises on platforms w
Should be fixed now.
Cheers,
Mike
John Hunter wrote:
> On Nov 26, 2007 9:48 AM, Jeff Whitaker <[EMAIL PROTECTED]> wrote:
>> Michael: I'm seeing the following error on OS X (Tiger) with numpy
>> 1.0.4 when building the latest svn transforms branch:
>
> And in mostly unrelated news, I'm seeing th
Michael Droettboom wrote:
> [Jeff -- I don't know why your original e-mail never got delivered to
> me, but I was able to see it in the archive.]
>
> The problem arises on platforms with 64-bit pointers -- in Numpy the
> datatype used to store the shape of an array is different from the
> dataty
[Jeff -- I don't know why your original e-mail never got delivered to
me, but I was able to see it in the archive.]
The problem arises on platforms with 64-bit pointers -- in Numpy the
datatype used to store the shape of an array is different from the
datatype used to specify the shape of an ar
On Nov 26, 2007 9:48 AM, Jeff Whitaker <[EMAIL PROTECTED]> wrote:
>
> Michael: I'm seeing the following error on OS X (Tiger) with numpy
> 1.0.4 when building the latest svn transforms branch:
And in mostly unrelated news, I'm seeing the following traceback on
zoom-to-rect from the toolbar in gtk
Michael: I'm seeing the following error on OS X (Tiger) with numpy
1.0.4 when building the latest svn transforms branch:
src/path.cpp: In member function 'Py::Object
_path_module::affine_transform(const Py::Tuple&)':
src/path.cpp:700: error: invalid conversion from 'npy_intp*' to 'int*'
cc1plu
11 matches
Mail list logo
