Skip to content
Snippets Groups Projects
Commit fde8c119 authored by Piotr Maślanka's avatar Piotr Maślanka
Browse files

ver bump

parent f4b2373e
No related branches found
No related tags found
1 merge request!6CoolAMQP 2.0.0
Pipeline #63423 passed with stages
in 2 minutes and 15 seconds
__version__ = '1.5.0' __version__ = '2.0.0a1'
...@@ -5,6 +5,7 @@ Welcome to CoolAMQP's documentation! ...@@ -5,6 +5,7 @@ Welcome to CoolAMQP's documentation!
:maxdepth: 2 :maxdepth: 2
:caption: Contents :caption: Contents
whatsnew
cluster cluster
tutorial tutorial
caveats caveats
......
What's new? What's new?
===========
CoolAMQP 2.0.0 marks a slight philosophy shift. Whereas 1.x used auto-generated UUID names, 2.0 will let the server
pick their names for themselves.
It also forbids some combinations of Queue arguments, and makes the default values more palatable, so for example
a naked :class:`coolamqp.objects.Queue` will be anonymous, non-durable, exclusive and auto-delete.
Queues
------
Following queues will fail now:
* auto_delete and durable
* anonymous and durables
* anonymous and not exclusives
* anonymous and not auto_delete
* auto_delete and not exclusive and not anonymous
Following will emit a warning:
* exclusive and auto_delete - DeprecationWarning, since they're removing it in RabbitMQ 4.0
* not anonymous, auto_delete and not exclusive - UserWarning, since this makes little sense
Anonymous queues
----------------
They are back. Besides, anything that you will pass to :meth:`coolamqp.clustering.Cluster.consume` will be declared, be
it an exchange, a queue or such shit. This allows you to declare anonymous queues.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment