[Numpy-discussion] question about memory ownership
Sat Jan 17 22:35:54 CST 2009
On Sat, Jan 17, 2009 at 11:23 PM, Robert Kern <firstname.lastname@example.org> wrote:
> On Sat, Jan 17, 2009 at 22:06, Darren Dale <email@example.com> wrote:
> > Hello,
> > Would someone be so kind as to explain how to create an ndarray subclass
> > that owns its own memory? I think RealisticInfoArray at
> > does not own its own memory, do you have to call ndarray.__new__
> > or is there another way?
> Does it matter? Unless if something actually digs down to grab the
> base object, the RealisticInfoArray object is the only thing keeping
> it alive. When it goes away, the underlying array goes away.
> But take a look at the implementation of memmap for a subclass that
> calls ndarray.__new__ directly.
I'm still working on my physical quantities package, and I want to prevent
something like the following:
That would give me qq in units of british thermal units, but it would also
modify the magnitude of q[:2]. It seems the most straight forward solution
is to simply disallow in-place modification of units when the array doesn't
own its own memory.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Numpy-discussion