Repository navigation
lxml 5.0.0 incompatibility - Arithmetic exception #277
Description
lxml 5.0.0 was released on Dec 29th 2023. This update causes an Arithmetic exception (core dumped) when using python-xmlsec.
Example code that would fail..
import xmlsec
from lxml import etree
root = None
with open("sign4-in.xml") as f:
root = etree.parse(f).getroot()
xmlsec.tree.add_ids(root, ["ID"])
Activity
xmlsec#277 - update lxml requirements
dev-python/xmlsec: broken with lxml-5
brianray commentedon Jan 17, 2024
also experiencing segfault with lxml-5
nosnilmot commentedon Jan 21, 2024
Use
pip install --no-binary lxml lxmlto install lxml from source and link to systemlibxml2, same asxmlsec, to avoid conflictinglibxml2libraries.See also https://bugs.launchpad.net/lxml/+bug/1960668#yui_3_10_3_1_1705879387759_1639 and https://github.com/nosnilmot/lxml/blob/master/doc/FAQ.txt#L623
eljeffeg commentedon Jan 31, 2024
@nosnilmot Sucks that your PR from Dec 2022 was never accepted. We could have avoided the entire issue. Suggest upvoting a fork. lol #275
bgaifullin commentedon Mar 2, 2024
I am not sure, that need to build lxml from source every-time.
nosnilmot commentedon Mar 3, 2024
what are you not sure about?
lxmlbundles it's own copy oflibxml2which may be a different version from the library thatxmlsecis linked against, the only way to ensure they are both using the same version is to rebuildlxml.This is documented here: https://lxml.de/FAQ.html#my-application-crashes
deronnax commentedon Mar 15, 2024
@eljeffeg you are on macOS, aren't you?
eljeffeg commentedon Mar 16, 2024
Yes, I'll try and test it tonight or tomorrow.
eljeffeg commentedon Mar 17, 2024
@deronnax I can confirm I was able to build the latest xmlsec on MacOS and it passed the example code posted in the issue description.