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

2024-12-27 Thread Israel, Daniel M via NumPy-Discussion
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 I thought it would require an entire custom array container, but the following trivial example actually shows the

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

2024-12-25 Thread Israel, Daniel M via NumPy-Discussion
Numerical Algorithms d...@lanl.gov On Dec 25, 2024, at 3:23 PM, Steven Ellis wrote: 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 mailto:numpy-discussion@python.org>> wrote: I was up

[Numpy-discussion] Copy on __setitem__

2024-12-25 Thread Israel, Daniel M via NumPy-Discussion
I was updating some code that uses a custom array container built with the mixin library. Specifically, I was trying to eliminate some warnings due to the change to the __array__ interface to add a copy argument. In doing so, I discovered that, for two objects u, v in my container class, the c