On Wed, May 9, 2012 at 2:34 PM, Ian Kelly wrote:
> On Wed, May 9, 2012 at 1:39 PM, Russell E. Owen wrote:
>> I was wondering. I override __new__ (and __init__) to print messages and
>> was quite surprised to only see __new__being called when the object was
>> first created, not when it was being
On Wed, May 9, 2012 at 1:39 PM, Russell E. Owen wrote:
> I was wondering. I override __new__ (and __init__) to print messages and
> was quite surprised to only see __new__being called when the object was
> first created, not when it was being unpickled. But maybe there's
> something funny about my
In article
,
Ian Kelly wrote:
> On Tue, May 8, 2012 at 1:19 PM, Russell E. Owen wrote:
> > In article ,
> > "Russell E. Owen" wrote:
> >
> >> What is the sequence of calls when unpickling a class with __setstate__?
>
> I believe it just calls object.__new__ followed by
> yourclass.__setstat
On Tue, May 8, 2012 at 1:19 PM, Russell E. Owen wrote:
> In article ,
> "Russell E. Owen" wrote:
>
>> What is the sequence of calls when unpickling a class with __setstate__?
I believe it just calls object.__new__ followed by
yourclass.__setstate__. So at the point __setstate__ is called, you
In article ,
"Russell E. Owen" wrote:
> What is the sequence of calls when unpickling a class with __setstate__?
>
> >From experimentation I see that __setstate__ is called and __init__ is
> not, but I think I need more info.
>
> I'm trying to pickle an instance of a class that is a subclass
What is the sequence of calls when unpickling a class with __setstate__?
>From experimentation I see that __setstate__ is called and __init__ is
not, but I think I need more info.
I'm trying to pickle an instance of a class that is a subclass of
another class that contains unpickleable objects.
