On Sun, Jan 18, 2009 at 07:17, Darren Dale wrote:
> Thanks for the advice. I'd like to look into the second option, since the
> former would not allow other in-place operations like *= /= **/.
That is a good use case.
> Hopefully
> the package will be fit to share with this list before too long
On Sat, Jan 17, 2009 at 11:44 PM, Robert Kern wrote:
> On Sat, Jan 17, 2009 at 22:35, Darren Dale wrote:
> >
> > On Sat, Jan 17, 2009 at 11:23 PM, Robert Kern
> wrote:
> >>
> >> On Sat, Jan 17, 2009 at 22:06, Darren Dale wrote:
> >> > Hello,
> >> >
> >> > Would someone be so kind as to explain
On Sat, Jan 17, 2009 at 22:35, Darren Dale wrote:
>
> On Sat, Jan 17, 2009 at 11:23 PM, Robert Kern wrote:
>>
>> On Sat, Jan 17, 2009 at 22:06, Darren Dale wrote:
>> > Hello,
>> >
>> > Would someone be so kind as to explain how to create an ndarray subclass
>> > that owns its own memory? I think
On Sat, Jan 17, 2009 at 11:23 PM, Robert Kern wrote:
> On Sat, Jan 17, 2009 at 22:06, Darren Dale 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
> >
> http://docs.scipy.org/doc/numpy/u
On Sat, Jan 17, 2009 at 22:06, Darren Dale 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
> http://docs.scipy.org/doc/numpy/user/basics.subclassing.html#basics-subclassing
> does not own its own
Hello,
Would someone be so kind as to explain how to create an ndarray subclass
that owns its own memory? I think RealisticInfoArray at
http://docs.scipy.org/doc/numpy/user/basics.subclassing.html#basics-subclassingdoes
not own its own memory, do you have to call ndarray.__new__ directly,
or is th
