On Tuesday 22 September 2009 13:14:55 Hrvoje Niksic wrote:
> Hans Meine wrote:
> > On Tuesday 22 September 2009 11:01:37 Hrvoje Niksic wrote:
> >> Is it intended for deserialization to uncouple arrays that share a
> >> common base?
> >
> > I think it's not really intended, but it's a limitation by
Hans Meine wrote:
> On Tuesday 22 September 2009 11:01:37 Hrvoje Niksic wrote:
>> Is it intended for deserialization to uncouple arrays that share a
>> common base?
>
> I think it's not really intended, but it's a limitation by design.
I wonder why a "base" attribute is even restored, then? If t
On Tuesday 22 September 2009 11:01:37 Hrvoje Niksic wrote:
> Is it intended for deserialization to uncouple arrays that share a
> common base?
I think it's not really intended, but it's a limitation by design.
AFAIK, it's related to Luca Citi's recent "ultimate base" thread - you simply
cannot en
Is it intended for deserialization to uncouple arrays that share a
common base? For example:
>>> import numpy, cPickle as p
>>> a = numpy.array([1, 2, 3]) # base array
>>> b = a[:] # view one
>>> b
array([1, 2, 3])
>>> c = a[::-1] # view two
>>> c
arr