I have a largish cython module that outputs the following warnings
every time I import the compiled module.
__main__:1: RuntimeWarning: numpy.dtype size changed, may indicate
binary incompatibility
__main__:1: RuntimeWarning: numpy.flatiter size changed, may indicate
binary incompatibility
Is thi
On 01.03.2012 19:33, Dag Sverre Seljebotn wrote:
Yeah, I proposed this on another thread as one of the options, but the
support wasn't overwhelming at the time...
I think it is worse to break parts of it, thus introducing bugs that
might go silent for a long time.
Rather deprecate the whole
On 03/01/2012 09:29 AM, Sturla Molden wrote:
On 01.03.2012 17:18, Dag Sverre Seljebotn wrote:
are saying we (somehow) stick with supporting "arr.shape[0]" in
the future, and perhaps even support "print arr.shape"? (+ arr.dim,
arr.strides).
What if you just deprecate ndarray support completely
On 01.03.2012 17:18, Dag Sverre Seljebotn wrote:
I'm anyway leaning towards deprecating arr.data, as it's too different
from what the Python attribute does.
This should be preferred, I think
&arr[0]
or
&arr[0]
The latter is exacty what arr.data will currently do in Cython (but not
On 01.03.2012 17:18, Dag Sverre Seljebotn wrote:
are saying we (somehow) stick with supporting "arr.shape[0]" in
the future, and perhaps even support "print arr.shape"? (+ arr.dim,
arr.strides).
What if you just deprecate ndarray support completely, and just focus on
memory views?
Yes, you
On 03/01/2012 04:03 AM, mark florisson wrote:
On 29 February 2012 17:57, Dag Sverre Seljebotn
wrote:
On 02/29/2012 09:42 AM, Stefan Behnel wrote:
Dag Sverre Seljebotn, 29.02.2012 18:06:
I'm wondering what the best course of action for deprecating the shape
field in numpy.pxd is.
The thing
On 29 February 2012 17:57, Dag Sverre Seljebotn
wrote:
> On 02/29/2012 09:42 AM, Stefan Behnel wrote:
>>
>> Dag Sverre Seljebotn, 29.02.2012 18:06:
>>>
>>> I'm wondering what the best course of action for deprecating the shape
>>> field in numpy.pxd is.
>>>
>>> The thing is, currently "shape" real
