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: http://cvs.zope.org/Zope3/lib/python/Persistence/cPersistence.c.diff?r1=1.9&r2=1.10 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 -- Florent Guillaume, Nuxeo (Paris, France) +33 1 40 33 79 87 http://nuxeo.com mailto:[EMAIL PROTECTED] _______________________________________________ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
