Release the new version

[mxamin]

Now that we have the fix for compliance with XMLsec v1.3.3, I guess we need to release a new version so we can close the related issue, trying to install with pip.
@jimjag @bgaifullin What do you think? Do you think of any preparation/changes before the release.
I can create the tag and the release note but since I don't have access to pypi, I need your help with that.

[ayakael]

I think y'all are still missing: #280 which makes the code changes for xmlsec 1.3.3.

[ayakael]

#253 will also be necessary for python 3.11 support, I believe. The code won't work as-is as it still references xmlSecCryptoAppKeyLoad rather than xmlSecCryptoAppKeyLoadEx. It can be merged, and adjusted after by replacing line 209 with key->handle = xmlSecCryptoAppKeyLoad(engine_and_key_id, xmlSecKeyDataTypePrivate, xmlSecKeyDataFormatEngine, NULL, xmlSecCryptoAppGetDefaultPwdCallback(),

[jimjag]

Both have been merged into HEAD

[ayakael]

Awesome! I made a mistake in the above comment. This final PR will fix things #285

[mxamin]

@ayakael #285 merged.

[ayakael]

Wicked! Build works on Alpine Linux using py3-lxml 4.94, py3-xmlsec 1.3.3 and python 3.11.

[mxamin]

With the new changes, you can't install the library using the old version of xmlsec1. I made a few changes to make it backward compatible: #286

[mxamin]

I also noticed that building the library would fail with the latest version of xmlsec1 (1.3.3) because of a typo: lsh123/xmlsec#755

[pitbulk]

Thanks to everyone involved in this hard work, keeping the project alive.

python3-saml depends on this great library and we are so happy that you are fixing the installation and other conflicts reported.

The release of a new version is so close, thanks again!

[nosnilmot]

I strongly suggest you merge #246 (at least until #283 is resolved)

[ryanhiebert]

@nosnilmot afaict, that PR doesn’t block binary lxml for library users, it’s just for the library tests or something. I don’t see that it is referenced from setup.py.

[nosnilmot]

that PR doesn’t block binary lxml for library users, it’s just for the library tests or something. I don’t see that it is referenced from setup.py.

oh boo, and from what I can tell there is no trivial way to specify 'no-binary' for dependencies installed by setup.py 😞

[jdoklovic]

is this going to be merged?

[jimjag]

We are at the point where, we think, all required and available PRs have been merged.