Actually that message is not quite helpful when trying to locate the
code which put that property there. There is almost zero context that
helps debugging. The traceback is worthless, because this happens in
What helps at least for me a _lot_ is the parent object's class and
the parent object state. This data is present in the method just needs
to be printed.
The printing/logging method can be negotiated I found this way of logging
some lines below.
Thursday, March 8, 2007, 5:09:29 PM, you wrote:
CW> Adam Groszer wrote:
>> Just run into a usual "Cannot pickle <type
>> 'zope.security._proxy._Proxy'> objects" exception.
CW> What does your patch give you that this error message doesn't?
>> + try:
>> + self._p.dump(state)
>> + except Exception, msg:
CW> it's logger msg, it's the exception object being caught.
>> + log = logging.getLogger("ZODB.serialize")
CW> Why get the logger here? get it in some global context.
Quote of the day:
You auto buy now.
For more information about ZODB, see the ZODB Wiki:
ZODB-Dev mailing list - ZODB-Dev@zope.org