[Numpy-discussion] potential bug in PyArray_MoveInto and PyArray_CopyInto?

[Charles R Harris]

On Thu, Jul 7, 2011 at 11:03 AM, James Bergstra
<bergstrj at iro.umontreal.ca>wrote:

> In numpy 1.5.1,  the functions PyArray_MoveInto and PyArray_CopyInto
> don't appear to treat strides correctly.
>
> Evidence:
> PyNumber_InPlaceAdd(dst, src), and modifies the correct subarray to
> which dst points.
>
> In the same context, PyArray_MoveInto(dst, src) modifies the first two
> rows of the
> underlying matrix instead of the first two columns. PyArray_CopyInto
> does the same.
>
> Is there something subtle going on here?
>
>
What are the strides/dims in src and dst?

Chuck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20110707/92238c1e/attachment.html>