On 31 January 2012 21:11, Dag Sverre Seljebotn
wrote:
> On 01/31/2012 09:53 PM, mark florisson wrote:
>>
>> On 31 January 2012 15:40, Dag Sverre Seljebotn
>> wrote:
>>>
>>> On 01/31/2012 03:29 PM, mark florisson wrote:
On 30 January 2012 21:03, Lisandro Dalcin wrote:
>
On 01/31/2012 09:53 PM, mark florisson wrote:
On 31 January 2012 15:40, Dag Sverre Seljebotn
wrote:
On 01/31/2012 03:29 PM, mark florisson wrote:
On 30 January 2012 21:03, Lisandro Dalcinwrote:
I'm testing my code with numpy-dev. They are trying to discourage use
of deprecated APIs, th
On 31 January 2012 15:40, Dag Sverre Seljebotn
wrote:
> On 01/31/2012 03:29 PM, mark florisson wrote:
>>
>> On 30 January 2012 21:03, Lisandro Dalcin wrote:
>>>
>>> I'm testing my code with numpy-dev. They are trying to discourage use
>>> of deprecated APIs, this includes direct access to the nda
On 31 January 2012 11:29, mark florisson wrote:
> On 30 January 2012 21:03, Lisandro Dalcin wrote:
>>
>> I think there is nothing Cython can do about this (other than
>> special-casing NumPy to disable this VERY useful warning).
>
> Weird, shouldn't you be getting an error? Because the size of th
On 01/31/2012 03:29 PM, mark florisson wrote:
On 30 January 2012 21:03, Lisandro Dalcin wrote:
I'm testing my code with numpy-dev. They are trying to discourage use
of deprecated APIs, this includes direct access to the ndarray struct.
In order to update your code, you have to pass -DNPY_NO_DEP
On 30 January 2012 21:03, Lisandro Dalcin wrote:
> I'm testing my code with numpy-dev. They are trying to discourage use
> of deprecated APIs, this includes direct access to the ndarray struct.
> In order to update your code, you have to pass -DNPY_NO_DEPRECATED_API
> to the C compiler (or #define
I'm testing my code with numpy-dev. They are trying to discourage use
of deprecated APIs, this includes direct access to the ndarray struct.
In order to update your code, you have to pass -DNPY_NO_DEPRECATED_API
to the C compiler (or #define it before including NumPy headers).
However, they have i
