Comment 5 for bug 98275
Revision history for this message
| Christian Theune (ctheune) wrote Re: [Bug 98275] Re: ZEO versus creative __getstate__ | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Am Mittwoch, den 10.10.2007, 15:14 +0000 schrieb Jim Fulton:
> Minor note. The bug is that changes to an object are registered
> while __getstate__ is being called.
Right. Thanks for pointing this out more explicitly than I did.
> I think the object should remain
> in the changed state until later. presumably the object is getting
> into the uptodate state too soon. This analysis is without looking
> at the code. :)
It looks like this happens because the object is new. When looking at
the example, an attribute is immediately changed and the state is
UPTODATE. When the serializiation later calls __getstate__ it is
UPTODATE as well.
Are new objects always UPTODATE?
--
gocept gmbh & co. kg - forsterstrasse 29 - 06112 halle/saale - germany
www.gocept.com - <email address hidden> - phone +49 345 122 9889 7 -
fax +49 345 122 9889 1 - zope and plone consulting and development