Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1455078

Summary: Update python-idna to version 2.5
Product: Red Hat Enterprise Linux 7 Reporter: Alfredo Moralejo <amoralej>
Component: python-idnaAssignee: Nathaniel McCallum <npmccallum>
Status: CLOSED DUPLICATE QA Contact: Namita Soman <nsoman>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.4CC: apevec, cheimes, mburns
Target Milestone: rcKeywords: Rebase
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1455346 (view as bug list) Environment:
Last Closed: 2017-08-10 14:07:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Alfredo Moralejo 2017-05-24 08:44:24 UTC
Description of problem:

Currently python-idna-2.0 is shipped in RHEL 7.3. This version consumes around 25MB of memory only to load:

>>> import resource
>>> resource.getrusage(resource.RUSAGE_SELF).ru_maxrss
5052
>>> import idna
>>> resource.getrusage(resource.RUSAGE_SELF).ru_maxrss
31344
>>> 

Some memory optimizations have been applied upstream from release 2.0 until latest one, 2.5 leading to a huge improvement:

>>> import resource
>>> resource.getrusage(resource.RUSAGE_SELF).ru_maxrss
5048
>>> import idna
>>> resource.getrusage(resource.RUSAGE_SELF).ru_maxrss
5888
>>> 

Reviewing the commits from v2.0..v2.5, there have been no changes in the public methods of the library, so it seems to be fully compatible with version 2.0, so i'd say it should be safe to update it.


OpenStack services using eventlet are using idna via import from python-dns, which is leading to increase memory usage.

I'm setting version 7.4, however i'm not sure if this request arrives on time to be included in 7.4 or needs to be moved to 7.5.

Comment 2 Christian Heimes 2017-08-10 14:00:17 UTC
This is a duplicate of #1425154.

There is no need to update python-idna to address the issue. RHEL 7.4 comes with python-idna-2.4-1.el7. Memory consumption of python-idna was addressed in upstream releases 2.1 and 2.3, https://github.com/kjd/idna/blob/master/HISTORY.rst . I requested errata https://access.redhat.com/errata/RHBA-2017:1996 for the same reason.

Comment 3 Christian Heimes 2017-08-10 14:07:26 UTC
I'm closing this BZ as duplicate. Please feel free to re-open the BZ if you a fix from python-idna 2.5.

*** This bug has been marked as a duplicate of bug 1425154 ***