Find a safer way to integrate with lxml about python-xmlsec HOT 5 CLOSED

@scoder is there a way check what version of libxml2 lxml is using via the C api?

Maybe a way to approach this is to check the libxml2 version being used by both lxml and xmlsec and raise and exception if it is not compatible.

It's not as elegant as your suggestion but it seems like an easier change to make and it would at least alert users of the issue instead of having to try to figure out what is causing a segfault.

from python-xmlsec.

Looks like python-xmlsec uses both the libxml APIs and the lxml C API 😅

Unfortunately it looks like this repo is pretty unmaintained at the moment (but here's hoping someone steps up to do something about that!).

from python-xmlsec.

I think @jimjag is gonna fork it. 🙏

from python-xmlsec.

@jonathangreen does it have to be C API?

from lxml import etree

print("%-20s: %s" % ('libxml used',      etree.LIBXML_VERSION))
print("%-20s: %s" % ('libxml compiled',  etree.LIBXML_COMPILED_VERSION))

from https://lxml.de/1.3/FAQ.html#i-think-i-have-found-a-bug-in-lxml-what-should-i-do

That's how I am testing a few combinations on macOS today with your xmlsec.get_libxml_version() in 3191662

from python-xmlsec.

@yhlee-tw it would be much easier if we could do the comparison in python but unfortunately the integration with lxml is done via the lxml c api. There really isn't any python code as part of this package.

I took a look at the lxml c api and I don't see a way to get the libxml2 version being used, but I was hoping @scoder or someone more familiar with the lxml c api might have a suggestion.

from python-xmlsec.