Changelog for python3-librabbitmq-2.0.0-8.1.x86_64.rpm :

* Sun Dec 08 2013 p.drouandAATTgmail.com- Update to version 1.0.3 + Fixed installation problem on OS X 10.9- Changes from version 1.0.2 + \"Bad Frame Read\" is now ConnectionError, not ChannelError. + Fixed problem with basic_cancel when disconnected. + Fixed typo Channel.recover -> Channel.basic_recover
* Thu Oct 24 2013 speilickeAATTsuse.com- Require python-setuptools instead of distribute (upstreams merged)
* Thu Jan 17 2013 toddrme2178AATTgmail.com- Update to version 1.0.1 - ``queue_unbind`` argument ``binding_key`` renamed to ``routing_key`` This change ensures compatibility with :mod:`amqp`. - Fixed memory leak caused by double call to ``AMQPTable_toPyDict`` - Fixed several potential memory leaks (Issue #15). - Removed `-ansi` compile option (Issue #17).- Update to version 1.0.0 - A channel exception will now cause the channel to be revived instead of simply closing the connection. - Support for lists and dictionaries in header values. This also means that the RabbitMQ `Bcc` and `CC` header extensions now can be constructured. - Support for float/double in header values. - Adds dummy ``nowait`` argument to ``queue_delete`` for amqplib API compatibility (it has no effect). - Library errors now use the correct error strings (Issue #7).- Update to version 0.9.9: - More llvm-gcc fixes for OS X.- Update to version 0.9.8 - Fixes bug when compiled using :program:`llvm-gcc` on OS X (Issue #5).- Update to version 0.9.7 - Connection and channel errors now close the connection, so that connection/channel cannot be used. Before an operation on a connection/channel that previously raised an exception would just hang. In the future it may be possible to have channel errors only close the channel, but this keeps it simple for now (and it works like amqplib).
* Mon Jun 18 2012 saschpeAATTsuse.de- Initial version