[lxml-dev] PyUnicodeUCS2_Decode errors

Ian Bicking ianb at colorstudy.com
Tue Feb 26 12:08:24 CST 2008

Stefan Behnel wrote:
> Hi Ian,
> Ian Bicking wrote:
>> Lately we've been having problems with errors like "undefined symbol:
>> PyUnicodeUCS2_Decode" when we do "import lxml.etree".  When we build
>> lxml from source the errors go away.
>> I'm guessing this is because of systems that use UCS4 instead of UCS2,
>> and lxml eggs that were compiled differently then the system.  Is this
>> the case?
> I guess so, yes.

I think I must be confusing something, as I realize now there aren't any 
Linux eggs on PyPI, just the tarballs.  (We have some private eggs we've 
built, and maybe those are what's causing the problem, but we'll have to 
investigate more.)


More information about the lxml mailing list