[PEAK] Recursive __setstate__ call

Phillip J. Eby pje at telecommunity.com
Fri Apr 16 21:25:22 EDT 2004

At 02:58 PM 4/16/04 +0200, Radek Kanovsky wrote:
>On Thu, Mar 25, 2004 at 11:52:02AM -0500, Phillip J. Eby wrote:
> > So, it's almost certainly something wrong with the state management logic
> > in _persistence.c.  It might be possible to workaround by having
> > 'setstate()' force ob._p_changed to a particular state before calling
> > __setstate__, but I'm not sure.
>Investigating persistence code I am almost sure that it is not
>possible to revive ghost object without setstate invocation as
>undesirable side effect. Any operation on ghost causes immediate
>_PyPersist_Load() -> setstate() calling.

What would happen if you temporarily set ob._p_jar to an object with a 
'setstate()' method that set the desired state?

More information about the PEAK mailing list