Skip to content
Snippets Groups Projects
Select Git revision
  • develop default
  • master
  • v1.5.0
  • v2.1.2
  • v2.1.1
  • v2.1.0
  • v2.0.0
  • v1.5.0
  • v1.4.3
  • v1.4.2
  • v1.4.1
  • v1.4.0
  • v1.3.1
  • v1.3.0
  • v1.2.16
  • v1.2.15
  • v1.2.14
  • v1.2.13
  • v1.2.12
  • v1.2.11
  • v1.2.10
  • v1.2.9
  • v1.2.8
23 results
Blame History Permalink
whatsnew.rst 1.16 KiB

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.

Cluster.publish

:meth:`coolamqp.clustering.Cluster.publish` has no longer the tx param, which has been deprecated.

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.