[
https://issues.apache.org/jira/browse/QPID-5925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl L. Pierce resolved QPID-5925.
------------------------------------
Resolution: Fixed
Fix Version/s: 0.26
Assignee: Darryl L. Pierce
I've applied the patches from QPID-5557 and QPID-5637 and generated a new
source tarball, 0.26.1. It's now pushed to PyPI.
https://pypi.python.org/pypi/qpid-python
> Requesting qpid-python on PyPi has 2 patches backported
> -------------------------------------------------------
>
> Key: QPID-5925
> URL: https://issues.apache.org/jira/browse/QPID-5925
> Project: Qpid
> Issue Type: Bug
> Components: Python Client
> Affects Versions: 0.26
> Environment: https://pypi.python.org/pypi/qpid-python
> Reporter: Brian Bouterse
> Assignee: Darryl L. Pierce
> Priority: Minor
> Fix For: 0.26
>
>
> It would be really great if the patches associated with QPID-5637 and
> QPID-5557 were applied to the Qpid 0.26 client bits offered through the
> qpid-python package. Currently my Kombu code monkey patches qpid.messaging
> for these two patches; it would be great to stop doing that. Some
> environments get their qpid bits from PyPi as a dependency for this Kombu
> code.
> qpid-python is available on PyPi [0], and currently has 0.26, but those two
> patches were not merged until the 0.28 release. Please apply the patches onto
> the package, and re-upload to PyPi. I'm not sure how PyPi handles multiple
> versions of the same release, but a new release of the same version (0.26)
> should be made.
> Once updated on PyPi, leave a comment and I can test it.
> [0]: https://pypi.python.org/pypi/qpid-python
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
