test failure with libxml2 2.11.1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxml |
Fix Released
|
Low
|
scoder |
Bug Description
While attempting to build lxml against the recently released libxml2 2.11.1:
[ 253s] Doctest: xpathxslt.txt
[ 253s] =======
[ 253s] ERROR: test_iterparse_
[ 253s] -------
[ 253s] Traceback (most recent call last):
[ 253s] File "/usr/lib64/
[ 253s] yield
[ 253s] File "/usr/lib64/
[ 253s] self._callTestM
[ 253s] File "/usr/lib64/
[ 253s] method()
[ 253s] File "/home/
[ 253s] elements = [el for _, el in self.etree.
[ 253s] File "/home/
[ 253s] elements = [el for _, el in self.etree.
[ 253s] File "src/lxml/
[ 253s] raise error
[ 253s] File "src/lxml/
[ 253s] done = self._read_
[ 253s] File "src/lxml/
[ 253s] return __FUNCTION_
[ 253s] File "src/lxml/
[ 253s] context.
[ 253s] File "src/lxml/
[ 253s] c_doc = self._handlePar
[ 253s] File "src/lxml/
[ 253s] return _handleParseRes
[ 253s] File "src/lxml/
[ 253s] _raiseParseErro
[ 253s] File "src/lxml/
[ 253s] raise error_log.
[ 253s] File "/tmp/tmp4pmacbxe", line 1
[ 253s] lxml.etree.
The release notes of libxml2 2.11.1 state a lot of symbols and deprecated functions are now removed, and also some security patches were addressed which may contribute to this issue.
I'm not sure the best way to handle this error. Any advice?
Changed in lxml: | |
status: | Fix Committed → Fix Released |
This might(!) get fixed with the next libxml2 release, 2.11.3, assuming that this is related:
https:/ /gitlab. gnome.org/ GNOME/libxml2/ -/commit/ 3463063001f36c1 6e5f6ce9ad33cd1 2a376fc874
Now that there is a 2.11.x release series, I'll probably use it for the lxml 5.0 binary wheels.