Comment 3 for bug 2048916

> Should everyone with this combination of xmlsec and livxml compile lxml themselves

At least, you have to take care that both use the same version of libxml2, or a compatible one. Otherwise, xmlsec cannot process libxml2 trees created by lxml. I tend to list the library versions provided by the binary wheels in the changelog.

The safest way to make sure both work nicely together is probably to do a source build for both. Or to install both from the Linux distribution rather than PyPI. Or from anaconda/condaforge.

> of can the prebuild package be changed?

The binary wheels of lxml include statically linked libraries so that users don't have to install those themselves. That allows doing "pip install lxml" without further prerequisites. IIUC, xmlsec depends on external libraries being installed. That would be possible also for lxml, but would mean that installing lxml becomes harder and for some users really difficult. It's probably acceptable for most users who want to use lxml yourself, but for many users, it's just a transitive dependency of something else. Making that harder to install is annoying at best.