[Zope-Coders] Zope 2.5.0beta3 & ParsedXML

[Matthew T. Kromer]

Hi Martijn,

The error is probably mine, since the 2.5.0 b3 went out the door with 
Pythons that I built late on Friday afternoon, and I think I tried to 
also build the pyexpat module (especially for the windows build).  Now, 
AFIAK, the windows build passed the pyexpat unit test, but that may not 
indicate all is well.  I remember trying to build pyexpat 1.95 (or 
whatever the version # is) in with the Solaris and Linux binaries as 
well, so its undoubtedly something goofy with expat; I was trying to do 
you a favor and include a newer expat with the solaris and linux 
Zopes -- just like the windows python distribution includes)

However, I can't tell you how to fix it, other than to recommend yanking 
the python that shipped with it and trying to build your own Python 
2.1.2 from CVS.


On Thursday, December 27, 2001, at 09:59 AM, Martijn Faassen wrote:

> Hi there,
>
> I've been trying ParsedXML with Zope 2.5.0 beta 3 in the hopes the 
> crashbug
> would go away. I've also downloaded the binary release instead of 
> building
> from sources myself.
>
> Unfortunately in this setup I am unable to upload XML documents that I 
> could
> before, including the 'Shakespeare test'.
>
> Instead, I get a variety of unicode errors from Expat and no matter
> how I change the sources to encode and decode and unicode, I can't get 
> the
> upload to work anymore. So something must've changed, either in Python 
> or
> in Zope, that causes this.
>
> When running the unittests I also get massive failures where there were
> none of this kind before, most seem to be along the lines of:
>
> UnicodeError: UTF-8 decoding error: unexpected code byte
>
> All of this did still work with Zope 2.5.0beta2.
>
> I'd really like a unicode/Expat expert to take a look at this. Perhaps
> Fred can. :)
>
> Regards,
>
> Martijn
>
>
> _______________________________________________
> Zope-Coders mailing list
> Zope-Coders@zope.org
> http://lists.zope.org/mailman/listinfo/zope-coders