Matthew T. Kromer <[EMAIL PROTECTED]> wrote:
> Well, the *sneaky* way to do it would be a funky one-time mod to the 
> object's __setstate__ method -- but I caution against excessive 
> sneakiness as potentially very frustrating to get right.

Which makes me think...

I don't find right now were was the thread that lead to this change:

But doesn't that mean that if an object is changed during its
__setstate__ but not after, those changes won't get persisted (because
just after __setstate__ the object reverts to UPTODATE) ?

Florent Guillaume, Nuxeo (Paris, France)
+33 1 40 33 79 87  mailto:[EMAIL PROTECTED]

Zope-Dev maillist  -  [EMAIL PROTECTED]
**  No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to