On 28/09/2010 00:12, Marius Gedminas wrote: > --- ./OFS/History.py.orig 2010-09-28 02:11:56.535745440 +0300 > +++ ./OFS/History.py 2010-09-28 02:12:00.043764683 +0300 > @@ -151,6 +151,9 @@ > base = aq_base(self) > base._p_activate() # make sure we're not a ghost > base.__setstate__(state) # change the state > + for attr in dir(base): > + if attr.startswith('_v_'): > + delattr(base, attr) > base._p_changed = True # marke object as dirty > self.manage_afterHistoryCopy()
Thanks, I guess I'll monkey patch for now, here's the bug: https://bugs.launchpad.net/zope2/+bug/649605 However, I'm curious, so the above will fix the object in the current thread, but what about objects in other threads? (or do _v_ attributes get killed off at the start of each transaction?) cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )