Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1764096 - Plans for continuing Python 2 support for python-dns?
Summary: Plans for continuing Python 2 support for python-dns?
Keywords:
Status: CLOSED DUPLICATE of bug 1849341
Alias: None
Product: Fedora
Classification: Fedora
Component: python-dns
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Paul Wouters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1824036
TreeView+ depends on / blocked
 
Reported: 2019-10-22 09:01 UTC by Paul Howarth
Modified: 2020-06-25 06:11 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-24 05:34:09 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Paul Howarth 2019-10-22 09:01:51 UTC 
Hi,

I'm the maintainer of trac-spamfilter-plugin, which has a dependency on python2-dns. The trac application and its plugins have not yet been ported to Python 3, so there is a co-ordination effort going on in #1737930 to check the ongoing support status of the necessary dependencies for trac and its plugins.

Are you OK with continuing support for python2-dns in Fedora 32 and possibly Fedora 33?

python2-dns has dependencies on python-crypto (which I maintain) and python2-typing (which is orphaned but I am in the process of taking it over). I am content to maintain these to support trac.
Comment 1 Paul Howarth 2020-01-07 11:03:33 UTC 
Please consider switching crypto backend from python-crypto to python-pycryptodomex (https://src.fedoraproject.org/rpms/python-dns/pull-request/1) so we can drop Python2 support from (dead upstream) python-crypto. I would like to move towards retiring python-crypto altogether at some point.
Comment 2 Avram Lubkin 2020-01-22 15:32:39 UTC 
Crypto support has been switched in rawhide.

Python 2 support is still in place, but I'm not sure how long that can be maintained. If upstream does a new release, which is long overdue, Python 2 will not be supported since they have already dropped support. It looks like trac has been working on this Python 3 support for 5 years but are finally starting to see there is urgency to get it done.
https://trac.edgewall.org/ticket/12130
Comment 3 Ben Cotton 2020-02-11 17:28:24 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.
Comment 4 Lumír Balhar 2020-06-24 05:34:09 UTC 
dnspython 2.0.0rc1 was released and I'll soon start with an update preparations (in COPR first). The version not only drops Python 2 but does a lot of incompatible changes so I have to proceed carefully.

It seems that only two packages depend on python2-dns:

$ dnf repoquery --repo=rawhide{,-source} --whatrequires python2-dns
mailman-3:2.1.33-1.fc33.src
mailman-3:2.1.33-1.fc33.x86_64
trac-spamfilter-plugin-0:1.4.0-0.2.20190829svn17127.fc32.noarch
trac-spamfilter-plugin-0:1.4.0-0.2.20190829svn17127.fc32.src

I won't update/drop Python 2 until all packages are ready for such a change. Please, follow bz#1849341 for updates.

*** This bug has been marked as a duplicate of bug 1849341 ***
Comment 5 Petr Špaček 2020-06-25 06:11:01 UTC 
(In reply to Lumír Balhar from comment #4)
> dnspython 2.0.0rc1 was released and I'll soon start with an update
> preparations (in COPR first). The version not only drops Python 2 but does a
> lot of incompatible changes so I have to proceed carefully.

Can you elaborate on the incompatible changes? We tried to be as compatible as possible.

If you find something surprising please open new issue similar to https://github.com/rthalley/dnspython/issues/480

Thanks.
Note You need to log in before you can comment on or make changes to this bug.