Project

Profile

Help

Refactor #1918

pulp depends on m2crypto, which will not be ported to Python 3

Added by rbarlow over 4 years ago. Updated almost 2 years ago.

Status:
CLOSED - NOTABUG
Priority:
High
Assignee:
-
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
Yes
Tags:
Sprint:
Quarter:

Description

According to http://fedora.portingdb.xyz/pkg/pulp/ our m2crypto dependency will not be ported to Python 3. We should move to something else (perhaps requests, or cryptography).


Related issues

Related to Pulp - Story #1866: As a user, I'd like pulp-admin to gracefully handle connection failuresCLOSED - WONTFIX

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by jcline@redhat.com over 4 years ago

+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?

#2 Updated by mhrivnak over 4 years ago

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

#3 Updated by mhrivnak over 4 years ago

  • Related to Story #1866: As a user, I'd like pulp-admin to gracefully handle connection failures added

#4 Updated by mhrivnak over 4 years ago

  • Tracker changed from Issue to Refactor
  • Priority changed from Normal to High

#5 Updated by semyers over 4 years ago

  • Tags Pulp 3 added

#6 Updated by semyers over 4 years ago

  • Sprint Candidate changed from No to Yes

#7 Updated by dalley almost 3 years ago

  • Status changed from NEW to CLOSED - NOTABUG

RPM plugin is being rewritten from scratch, so, refactor is not really applicable.

#8 Updated by daviddavis almost 2 years ago

  • Sprint/Milestone set to 3.0.0

#9 Updated by bmbouter almost 2 years ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF