Pulp

+1 to python-cryptography (https://cryptography.io/en/latest/). Docs are very good and the project is very actively maintained.

The only place M2Crypto is used in pulp_rpm is https://github.com/pulp/pulp_rpm/blob/81a99f7304e6da3cf193a8bb815d9678f17b7f60/plugins/pulp_rpm/yum_plugin/util.py#L64

There are a lot of hits in platform, but almost all of it is in playpen (that really needs a clean-up). There is some in the agent code, which is unfortunate since python-cryptography (as of the latest version, anyway) only supported Python 2.6+. I'm not sure what we'll do about that. Is requiring an SCL to run the agent too much to ask? Are we dropping the agent soon enough that it doesn't matter?

The "bindings" in platform also use m2crypto. I think that and the agent code use it right now because they both have to run in python 2.4 on EL5, and options there are limited.

The plan is to still drop the agent in 3.0, so that will eliminate some of the use. We will definitely drop the agent code before moving to python 3. :)

Once we drop the agent, that will drop the python 2.4 requirement. We can then convert the bindings to use something else. Presumably we can just have it use "requests" and be done? That is tracked here:

https://pulp.plan.io/issues/1866