@ayakael you linked to a codespace (which can't be accessed). Did you mean #253?

for info, and unless I am wrong, #253 which you say you need, introduces another use of xmlSecCryptoAppKeyLoad (the one you commented) but you don't correct it in your PR. So if #253 get merged and then yours, the problem still happens

@deronnax This PR only adjusts the codebase as it is. I already alerted of this issue on #253 . Ideally, the author should update that, but if they don't and it is merged I can adjust this it in this PR.

But in the first message of this PR, you say #253 is a requirement for this PR, so when this PR is merged, #253 will have been too, no?

But in the first message of this PR, you say #253 is a requirement for this PR, so when this PR is merged, #253 will have been too, no?

It doesn't actually require it. Sorry for the confusion. This PR can be merged as-is.

I forget a few doc changes that I just pushed now

@bgaifullin just merging this would fix the current compatibility issue with current libxml, thus fixing python-xmlsec for everyone, and turn the CI back to green. Would you please merge this?

Is it possible to release new version because this PR? 🤔