[Numpy-discussion] Cython issues w/ 1.4.0

David Cournapeau cournape@gmail....
Tue Dec 8 11:28:46 CST 2009


On Wed, Dec 9, 2009 at 2:02 AM, Pauli Virtanen <pav+sp@iki.fi> wrote:
> Sun, 06 Dec 2009 14:53:58 +0100, Gael Varoquaux wrote:
>> I have a lot of code that has stopped working with my latest SVN pull to
>> numpy.
>>
>> * Some compiled code yields an error looking like (from memory):
>>
>>     "incorrect type 'numpy.ndarray'"
>
> This, by the way, also affects the 1.4.x branch. Because of the datetime
> branch merge, a new field was added to ArrayDescr -- and this breaks
> previously compiled Cython modules.

It seems that it is partly a cython problem. If py3k can be done for
numpy 1.5, I wonder if we should focus on making incompatible numpy
1.6 (or 2.0 :) ), with an emphasis on making the C api more robust
about those changes, using opaque pointer, functions, etc...
Basically, implementing something like PEP 384, but for numpy.

As numpy becomes more and more used as a basic for so many softwares,
I feel like the current situation is hurting numpy users quite badly.
Maybe I am overestimate the problem, though ?

cheers,

David


More information about the NumPy-Discussion mailing list