-
Notifications
You must be signed in to change notification settings - Fork 106
importing on macOS fails with symbol not found #346
New issue
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
Comments
Error does not occur when using xmlsec 1.3.14, btw |
nijel
added a commit
to nijel/weblate
that referenced
this issue
Mar 25, 2025
Let's take same approach as we already do on Linux as these wheels are always causing some issues. See also xmlsec/python-xmlsec#346
nijel
added a commit
to nijel/weblate
that referenced
this issue
Mar 25, 2025
Let's take same approach as we already do on Linux as these wheels are always causing some issues. See also xmlsec/python-xmlsec#346
nijel
added a commit
to nijel/weblate
that referenced
this issue
Mar 25, 2025
Let's take same approach as we already do on Linux as these wheels are always causing some issues. See also xmlsec/python-xmlsec#346
nijel
added a commit
to nijel/weblate
that referenced
this issue
Mar 25, 2025
Let's take same approach as we already do on Linux as these wheels are always causing some issues. See also xmlsec/python-xmlsec#346
nijel
added a commit
to nijel/weblate
that referenced
this issue
Mar 25, 2025
The xmlsec is currently not working on macos, but that should not block rest of the code. See also xmlsec/python-xmlsec#346
nijel
added a commit
to WeblateOrg/weblate
that referenced
this issue
Mar 25, 2025
The xmlsec is currently not working on macos, but that should not block rest of the code. See also xmlsec/python-xmlsec#346
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On macOS 15.3.1 (GitHub Actions) importing xmlsec fails:
The CI log for this is at https://github.com/WeblateOrg/weblate/actions/runs/13947483456/job/39038029295
The text was updated successfully, but these errors were encountered: