Bug 1298167

Created attachment 1114378 [details]
add support for python3

Features also to run tests, some of them need a running rabbitmq-server.

Created attachment 1114395 [details]
add support for python3

Features also to run tests, some need a running instance of rabbitmq-server.

I'll try to send a better patch (without direct calls of 2to3 or modernize) to upstream.

(In reply to Raphael Groner from comment #3)
> I'll try to send a better patch (without direct calls of 2to3 or modernize)
> to upstream.

Hi, Raphael.  I'm watching this issue so I pick up your improved patch.  Once you attach it, I'll get it reviewed.

Setting priority to not forget about this bug.

Are you aware about the GitHub mirror¹ of Qpid and especially python module? I see a lot of patches there, done after the 0.32 release. Maybe it's reasonable to update the package to some post-release?

While my tries to create a proper python3 patch, I detect a lot of hacks for older python (version 2.3) in the sources that do not work after 2to3 tool's applied.

¹ https://github.com/apache/qpid/tree/trunk/qpid/python

If it helps, I believe the official upstream repos are here and appear active:

https://git1-us-west.apache.org/repos/asf?a=project_list&s=qpid

Proton specifically claims to have PY3 support merged as of Jun 22, 2015.

http://qpid.2158936.n2.nabble.com/Python-3-port-is-done-td7623782.html

Ping? Any news here?

python-qpid-1.37.0-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-0233f4ea2e

python-qpid-1.37.0-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-432cb6bb51

python-qpid-1.37.0-1.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-81c89b85c0

This component does not support python 3.

(In reply to Irina Boverman from comment #12)
> This component does not support python 3.

I still fail to understand why you reference this bug with the explicit request for python3 support.

python-qpid-1.37.0-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-0233f4ea2e

python-qpid-1.37.0-1.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-81c89b85c0

python-qpid-1.37.0-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-432cb6bb51

python-qpid-1.37.0-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.

python-qpid-1.37.0-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.

python-qpid-1.37.0-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.

Not fixed. Again, please do not reference bugs without validation.

What is the status here? Should the packages be dropped instead?

Well, at least there seems to be some preparation work for switching to another python.
https://src.fedoraproject.org/rpms/python-qpid/c/faeb6e5cc54874f607f158f273c2e95b645ace36

(In reply to Irina Boverman from comment #12)
> This component does not support python 3.

Does this statement still count?

I was about to retire the Python support in saslwrapper (bug 1738175) when I noticed that python-qpid still depends on it.

But it seems like upstream maintenance of these packages has totally stopped. There is the "new" Qpid Proton implementation and upstream seems to prefer that over the original qpid-python.

Maybe it is time to just retire this group of packages (python-qpid, qpid-cpp, saslwrapper)?

For example, in 2016 this issue with closed as wontfix: https://issues.apache.org/jira/browse/QPID-3668

"Forward development for Python is now focused on the Proton Python binding. As a result, we are considering only defects and minor improvements for the Python qpid.messaging API. These issues are closed "won't fix" because they are improvements outside of that scope."

and in 2017 when asked about Python 3 support: https://mail-archives.apache.org/mod_mbox/qpid-users/201712.mbox/%3CCAFcPDB9vOr_7sYqJA-3b0YF5%3DkP9aSi8aNNDrDA_NOSnYoyZ4A%40mail.gmail.com%3E

"I'm not aware of any plans to work on Python 3 support for qpid-python,
although it's possible somebody else has an interest in it. If you are
interested in working on it yourself, open a JIRA and attach patches, we
can get them applied to a future release."

(which itself seems to be at odds with the earlier statement about closing JIRA issues.)

Automation has figured out the package is retired in rawhide.

If you like it to be unretired, please open a ticket at https://pagure.io/releng/new_issue?template=package_unretirement

Really sad for the invested time but it seems to be like that.

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days