[zope2-tracker] [Bug 195761] Re: XML export producesAttributeError unicode

[ke1g]

For what it's worth, this doesn't seem to be because of any effort to encode into XML, but rather
is a failure of the ToXMLUnpickler, which is trying to convert from a pickle (loaded from a _storage
object on a Connection object - zopedb?) to Python, so that that can later be XML encoded.  The
stack has lots of instances of classes from ...xml.ppml but the last object, which happens to be the
title of the blog, was appended as a unicode string, rather than an object of some kind.  The current
operation is trying to add an id to the "last" object and you can't add attributes to a Unicode object.
You can't add them to string objects either, which is why, I'd guess, that ppml has this fancy String
class.

So I'm guessing that ToXMLUnpickler just has failed to keep up with changes to the format of the
pickles coming from the zopedb.  Too bad this can't be shared code with whatever unpickles an
object when it is awakened (that's been kept up to date).

I'm already way beyond my zope depth, and out of time to look at this.  I'm posting in hope that
my info might jog a real zope deveolper into saying: "Oh!  That's simple."

(Exporting a Quills blog: Plone 3.2.1 Zope 2.10.6-final, python 2.4.6,
linux2)

-- 
XML export producesAttributeError unicode
https://bugs.launchpad.net/bugs/195761
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.