Partly erratic wrong behaviour, Python 3, lxml

Fri Mar 5 03:03:36 EST 2010

Jussi Piitulainen, 04.03.2010 22:40:
> Stefan Behnel writes:
>> Jussi Piitulainen, 04.03.2010 11:46:
>>> I am observing weird semi-erratic behaviour that involves Python 3
>>> and lxml, is extremely sensitive to changes in the input data, and
>>> only occurs when I name a partial result. I would like some help
>>> with this, please. (Python 3.1.1; GNU/Linux; how do I find lxml
>>> version?)
>>>> Here's how to find the version:
>>>> http://codespeak.net/lxml/FAQ.html#i-think-i-have-found-a-bug-in-lxml-what-should-i-do
>> Ok, thank you. Here's the results:
>> >>> print(et.LXML_VERSION, et.LIBXML_VERSION,
> ... et.LIBXML_COMPILED_VERSION, et.LIBXSLT_VERSION,
> ... et.LIBXSLT_COMPILED_VERSION)
> (2, 2, 4, 0) (2, 6, 26) (2, 6, 26) (1, 1, 17) (1, 1, 17)

I can't reproduce this with the latest lxml trunk (and Py3.2 trunk) and 
libxml2 2.7.6, even after running your test script for quite a while. I'd 
try to upgrade the libxml2 version.
Stefan