[lxml-dev] Test Failures in lxml 1.3.2

Stefan Behnel stefan_ml at behnel.de
Thu Jul 12 10:11:41 CEST 2007


jholg at gmx.de wrote:
>> It seems like the problem only arises on UCS-2 systems. Could anyone with
>> a
>> UCS-2 Linux system check if this is also fails there? UCS-2 can be
>> detected
>> with "sys.maxunicode" being 65535 (I think). UCS-4 systems say 1114111
>> here. I
> 
> Runs without failures on Solaris with sys.maxunicode==65535:

Thanks for testing. Just to be sure, Sun Solaris machines are big endian,
right? Intel is little endian, so Solaris actually uses a different byte
encoding here.

So I think we can restrict the problem to UCS-2 little endian. Any
non-Windows, non-Mac-OS-X testers for that one?

Or maybe any Mac-OS PPC testers?


> Note that I ran from 1.3 branch, not 1.3.2 release (found not 1.3.2 tag in the repository)

Thanks for reminding me. It's there now.


> so maybe the offending test has been disabled already (?)

No, it's still in there.

Stefan



More information about the lxml-dev mailing list