[Numpy-discussion] Re: [EXTERNAL] Copy on __setitem__

On Thu, Dec 26, 2024 at 5:48 PM Benjamin Root via NumPy-Discussion < numpy-discussion@python.org> wrote: > Seems to make sense to me? Or is the following a bug? > > >>> import numpy as np > >>> u = np.zeros(5) > >>> v = np.ones(5) > >>> u > array([0., 0., 0., 0., 0.]) > >>> u[...] = v > >>> u > ar

[Numpy-discussion] Re: [EXTERNAL] Copy on __setitem__

Seems to make sense to me? Or is the following a bug? >>> import numpy as np >>> u = np.zeros(5) >>> v = np.ones(5) >>> u array([0., 0., 0., 0., 0.]) >>> u[...] = v >>> u array([1., 1., 1., 1., 1.]) >>> v[4] = 5 >>> v array([1., 1., 1., 1., 5.]) >>> u array([1., 1., 1., 1., 1.]) If you don't do a

[Numpy-discussion] Re: Copy on __setitem__

Hi David, New to the listserv, but, maybe you can provide a reproducible example? Steven On Wed, Dec 25, 2024, 2:19 PM Israel, Daniel M via NumPy-Discussion < numpy-discussion@python.org> wrote: > I was updating some code that uses a custom array container built with the > mixin library. Speci

[Numpy-discussion] Re: [EXTERNAL] Copy on __setitem__

It looks like general assignment function `array_assign_subscript` calls `PyArray_CopyObject(view, op)` link which in turn always calls `PyArray_DiscoverDTypeAndShape` with `cop

[Numpy-discussion] Re: [EXTERNAL] Copy on __setitem__

That seems like a bug but not sure why it would happen. It needs to call `__array__`, but indeed of course not with `copy=True`. Would you open an issue on github? - Sebastian On Thu, 2024-12-26 at 03:46 +, Israel, Daniel M via NumPy- Discussion wrote: > Sure.  I didn’t originally, because