We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi Team,
It seems like we cannot import the xmlsec package because of this error.
Is there a matrix that we need to look into to make sure the xmlsec can be imported properly and we can install the right version on the system.
-- root@serv:/# pip freeze | grep lxml lxml==5.2.1 root@serv:/# pip freeze | grep xmlsec xmlsec==1.3.14
libxml2/now 2.9.13+dfsg-1ubuntu0.4 arm64 [installed,local] xmlsec1/now 1.2.33-1build2 arm64 [installed,local]
Python 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] on linux Type "help", "copyright", "credits" or "license" for more information.
import xmlsec Traceback (most recent call last): File "", line 1, in xmlsec.InternalError: (-1, 'lxml & xmlsec libxml2 library version mismatch')
KeyboardInterrupt
The text was updated successfully, but these errors were encountered:
Closing it because of being duplicate of #316. Let's continue there :)
Sorry, something went wrong.
No branches or pull requests
Hi Team,
It seems like we cannot import the xmlsec package because of this error.
Is there a matrix that we need to look into to make sure the xmlsec can be imported properly and we can install the right version on the system.
--
root@serv:/# pip freeze | grep lxml
lxml==5.2.1
root@serv:/# pip freeze | grep xmlsec
xmlsec==1.3.14
libxml2 version
libxml2/now 2.9.13+dfsg-1ubuntu0.4 arm64 [installed,local]
xmlsec1/now 1.2.33-1build2 arm64 [installed,local]
Here's the error I get when importing it
Python 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
KeyboardInterrupt
The text was updated successfully, but these errors were encountered: