2012-06-07 14:22:02 +00:00
========================================
2013-11-03 15:24:32 +00:00
kombu - Messaging library for Python
2012-06-07 14:22:02 +00:00
========================================
2010-06-23 10:08:39 +00:00
2020-10-08 21:00:26 +00:00
|build-status| |coverage| |license| |wheel| |pyversion| |pyimp| |downloads|
2015-02-01 20:13:35 +00:00
2024-09-19 12:25:14 +00:00
:Version: 5.4.2
2018-10-19 15:39:42 +00:00
:Documentation: https://kombu.readthedocs.io/
2018-06-10 10:40:04 +00:00
:Download: https://pypi.org/project/kombu/
2016-04-11 20:02:34 +00:00
:Source: https://github.com/celery/kombu/
:Keywords: messaging, amqp, rabbitmq, redis, mongodb, python, queue
About
=====
2010-06-23 10:08:39 +00:00
2013-11-03 15:24:32 +00:00
`Kombu` is a messaging library for Python.
2010-11-12 14:47:29 +00:00
2010-11-11 15:00:44 +00:00
The aim of `Kombu` is to make messaging in Python as easy as possible by
2012-06-07 14:22:02 +00:00
providing an idiomatic high-level interface for the AMQ protocol, and also
2010-11-12 14:54:29 +00:00
provide proven and tested solutions to common messaging problems.
2010-11-12 14:22:23 +00:00
2012-06-07 14:25:27 +00:00
`AMQP`_ is the Advanced Message Queuing Protocol, an open standard protocol
for message orientation, queuing, routing, reliability and security,
for which the `RabbitMQ`_ messaging server is the most popular implementation.
2012-06-07 14:22:02 +00:00
2010-11-12 14:22:23 +00:00
Features
========
* Allows application authors to support several message server
solutions by using pluggable transports.
2021-09-07 05:24:10 +00:00
* AMQP transport using the `py-amqp`_ , or `qpid-python`_ libraries.
2012-06-06 13:46:58 +00:00
2010-11-12 14:22:23 +00:00
* Virtual transports makes it really easy to add support for non-AMQP
2016-08-18 23:18:25 +00:00
transports. There is already built-in support for `Redis`_ ,
2020-06-13 21:28:57 +00:00
`Amazon SQS`_ , `ZooKeeper`_ , `SoftLayer MQ`_ , `MongoDB`_ and `Pyro`_ .
2010-11-12 14:22:23 +00:00
* In-memory transport for unit testing.
* Supports automatic encoding, serialization and compression of message
payloads.
* Consistent exception handling across transports.
* The ability to ensure that an operation is performed by gracefully
2011-11-02 02:39:48 +00:00
handling connection and channel errors.
2010-10-27 08:34:28 +00:00
2010-11-12 14:22:23 +00:00
* Several annoyances with `amqplib`_ has been fixed, like supporting
timeouts and the ability to wait for events on more than one channel.
2010-10-27 08:34:28 +00:00
2010-11-12 14:22:23 +00:00
* Projects already using `carrot`_ can easily be ported by using
a compatibility layer.
2010-10-27 08:34:28 +00:00
2010-11-12 14:47:29 +00:00
For an introduction to AMQP you should read the article `Rabbits and warrens`_ ,
and the `Wikipedia article about AMQP`_ .
2017-05-30 13:53:40 +00:00
.. _`RabbitMQ`: https://www.rabbitmq.com/
.. _`AMQP`: https://amqp.org
2018-06-10 10:40:04 +00:00
.. _`py-amqp`: https://pypi.org/project/amqp/
.. _`qpid-python`: https://pypi.org/project/qpid-python/
2017-05-30 13:53:40 +00:00
.. _`Redis`: https://redis.io
.. _`Amazon SQS`: https://aws.amazon.com/sqs/
2012-06-07 12:08:41 +00:00
.. _`Zookeeper`: https://zookeeper.apache.org/
2018-01-16 03:18:44 +00:00
.. _`Rabbits and warrens`: http://web.archive.org/web/20160323134044/http://blogs.digitar.com/jjww/2009/01/rabbits-and-warrens/
2017-05-30 13:53:40 +00:00
.. _`amqplib`: https://barryp.org/software/py-amqplib/
.. _`Wikipedia article about AMQP`: https://en.wikipedia.org/wiki/AMQP
2018-06-10 10:40:04 +00:00
.. _`carrot`: https://pypi.org/project/carrot/
.. _`librabbitmq`: https://pypi.org/project/librabbitmq/
2018-11-25 14:40:54 +00:00
.. _`Pyro`: https://pyro4.readthedocs.io/
2017-05-30 13:53:40 +00:00
.. _`SoftLayer MQ`: https://sldn.softlayer.com/reference/messagequeueapi
2020-06-13 21:28:57 +00:00
.. _`MongoDB`: https://www.mongodb.com/
2010-06-23 10:10:02 +00:00
2013-04-11 12:45:21 +00:00
.. _transport-comparison:
2011-01-18 08:20:13 +00:00
Transport Comparison
====================
2015-11-07 15:55:55 +00:00
+---------------+----------+------------+------------+---------------+--------------+-----------------------+
| **Client** | **Type** | **Direct** | **Topic** | **Fanout** | **Priority** | **TTL** |
+---------------+----------+------------+------------+---------------+--------------+-----------------------+
| *amqp* | Native | Yes | Yes | Yes | Yes [#f3]_ | Yes [#f4]_ |
+---------------+----------+------------+------------+---------------+--------------+-----------------------+
| *qpid* | Native | Yes | Yes | Yes | No | No |
+---------------+----------+------------+------------+---------------+--------------+-----------------------+
| *redis* | Virtual | Yes | Yes | Yes (PUB/SUB) | Yes | No |
+---------------+----------+------------+------------+---------------+--------------+-----------------------+
| *mongodb* | Virtual | Yes | Yes | Yes | Yes | Yes |
+---------------+----------+------------+------------+---------------+--------------+-----------------------+
| *SQS* | Virtual | Yes | Yes [#f1]_ | Yes [#f2]_ | No | No |
+---------------+----------+------------+------------+---------------+--------------+-----------------------+
| *zookeeper* | Virtual | Yes | Yes [#f1]_ | No | Yes | No |
+---------------+----------+------------+------------+---------------+--------------+-----------------------+
| *in-memory* | Virtual | Yes | Yes [#f1]_ | No | No | No |
+---------------+----------+------------+------------+---------------+--------------+-----------------------+
| *SLMQ* | Virtual | Yes | Yes [#f1]_ | No | No | No |
+---------------+----------+------------+------------+---------------+--------------+-----------------------+
2018-11-25 14:40:54 +00:00
| *Pyro* | Virtual | Yes | Yes [#f1]_ | No | No | No |
+---------------+----------+------------+------------+---------------+--------------+-----------------------+
2012-01-20 23:13:14 +00:00
.. [#f1] Declarations only kept in memory, so exchanges/queues
must be declared by all clients that needs them.
.. [#f2] Fanout supported via storing routing tables in SimpleDB.
2012-01-27 17:23:49 +00:00
Disabled by default, but can be enabled by using the
`` supports_fanout `` transport option.
2011-06-13 14:51:01 +00:00
2014-05-08 05:06:49 +00:00
.. [#f3] AMQP Message priority support depends on broker implementation.
2011-01-18 08:20:13 +00:00
2015-11-07 15:55:55 +00:00
.. [#f4] AMQP Message/Queue TTL support depends on broker implementation.
2010-10-27 08:34:28 +00:00
Documentation
-------------
2012-06-06 13:46:58 +00:00
Kombu is using Sphinx, and the latest documentation can be found here:
2010-10-27 08:34:28 +00:00
2016-05-29 14:08:27 +00:00
https://kombu.readthedocs.io/
2010-10-27 08:34:28 +00:00
Quick overview
--------------
2016-10-15 00:55:10 +00:00
2016-10-31 19:39:19 +00:00
.. code :: python
2010-10-27 12:22:29 +00:00
2012-06-24 15:32:17 +00:00
from kombu import Connection, Exchange, Queue
2010-06-23 10:10:02 +00:00
2012-06-24 15:32:17 +00:00
media_exchange = Exchange('media', 'direct', durable=True)
video_queue = Queue('video', exchange=media_exchange, routing_key='video')
2010-06-23 10:10:02 +00:00
2011-10-09 15:46:37 +00:00
def process_media(body, message):
2022-08-03 02:50:48 +00:00
print(body)
2011-10-09 15:46:37 +00:00
message.ack()
2011-09-07 13:41:17 +00:00
# connections
2012-06-24 15:32:17 +00:00
with Connection('amqp://guest:guest@localhost//') as conn:
2010-06-23 10:10:02 +00:00
2011-09-07 13:41:17 +00:00
# produce
2013-10-02 13:43:19 +00:00
producer = conn.Producer(serializer='json')
producer.publish({'name': '/tmp/lolcat1.avi', 'size': 1301013},
exchange=media_exchange, routing_key='video',
declare=[video_queue])
2012-06-11 17:25:12 +00:00
2013-10-02 13:43:19 +00:00
# the declare above, makes sure the video queue is declared
2012-06-11 17:25:12 +00:00
# so that the messages can be delivered.
# It's a best practice in Kombu to have both publishers and
2016-08-18 23:18:25 +00:00
# consumers declare the queue. You can also declare the
2012-06-11 17:25:12 +00:00
# queue manually using:
# video_queue(conn).declare()
2010-06-23 10:10:02 +00:00
2011-09-07 13:41:17 +00:00
# consume
with conn.Consumer(video_queue, callbacks=[process_media]) as consumer:
# Process messages and handle events on all channels
while True:
2011-10-09 15:46:37 +00:00
conn.drain_events()
2010-06-23 10:10:02 +00:00
2010-10-27 08:34:28 +00:00
# Consume from several queues on the same channel:
2012-06-24 15:32:17 +00:00
video_queue = Queue('video', exchange=media_exchange, key='video')
image_queue = Queue('image', exchange=media_exchange, key='image')
2010-06-23 10:10:02 +00:00
2011-09-07 13:41:17 +00:00
with connection.Consumer([video_queue, image_queue],
callbacks=[process_media]) as consumer:
while True:
connection.drain_events()
2016-04-07 22:59:26 +00:00
Or handle channels manually:
2016-10-15 00:55:10 +00:00
2016-10-31 19:39:19 +00:00
.. code :: python
2011-09-07 13:41:17 +00:00
with connection.channel() as channel:
producer = Producer(channel, ...)
2024-06-24 11:43:18 +00:00
consumer = Consumer(channel)
2011-09-07 13:41:17 +00:00
All objects can be used outside of with statements too,
2016-04-07 22:59:26 +00:00
just remember to close the objects after use:
2016-10-15 00:55:10 +00:00
2016-10-31 19:39:19 +00:00
.. code :: python
2011-09-07 13:41:17 +00:00
2012-06-24 15:32:17 +00:00
from kombu import Connection, Consumer, Producer
2011-09-07 13:41:17 +00:00
2012-06-24 15:32:17 +00:00
connection = Connection()
2011-09-07 13:41:17 +00:00
# ...
2013-10-02 13:43:19 +00:00
connection.release()
2011-09-07 13:41:17 +00:00
consumer = Consumer(channel_or_connection, ...)
consumer.register_callback(my_callback)
2010-07-22 14:09:18 +00:00
consumer.consume()
2011-09-07 13:41:17 +00:00
# ....
consumer.cancel()
2010-07-22 14:09:18 +00:00
2010-10-27 08:34:28 +00:00
`Exchange` and `Queue` are simply declarations that can be pickled
2011-11-02 02:39:48 +00:00
and used in configuration files etc.
2010-06-29 15:44:24 +00:00
2010-11-11 15:00:44 +00:00
They also support operations, but to do so they need to be bound
2012-06-19 14:57:59 +00:00
to a channel.
Binding exchanges and queues to a connection will make it use
that connections default channel.
2016-10-15 00:55:10 +00:00
2016-04-11 20:02:34 +00:00
::
2010-06-29 15:44:24 +00:00
2012-06-24 15:32:17 +00:00
>>> exchange = Exchange('tasks', 'direct')
2010-06-29 15:44:24 +00:00
2012-06-24 15:32:17 +00:00
>>> connection = Connection()
2012-06-19 14:57:59 +00:00
>>> bound_exchange = exchange(connection)
2010-06-29 15:44:24 +00:00
>>> bound_exchange.delete()
# the original exchange is not affected, and stays unbound.
>>> exchange.delete()
raise NotBoundError: Can't call delete on Exchange not bound to
a channel.
2010-06-23 10:08:39 +00:00
Terminology
===========
There are some concepts you should be familiar with before starting:
2010-06-29 19:12:29 +00:00
* Producers
2010-06-23 10:08:39 +00:00
2010-06-29 19:12:29 +00:00
Producers sends messages to an exchange.
2010-06-23 10:08:39 +00:00
* Exchanges
Messages are sent to exchanges. Exchanges are named and can be
configured to use one of several routing algorithms. The exchange
routes the messages to consumers by matching the routing key in the
message with the routing key the consumer provides when binding to
the exchange.
* Consumers
Consumers declares a queue, binds it to a exchange and receives
messages from it.
* Queues
Queues receive messages sent to exchanges. The queues are declared
by consumers.
* Routing keys
2016-08-18 23:18:25 +00:00
Every message has a routing key. The interpretation of the routing
2010-06-23 10:08:39 +00:00
key depends on the exchange type. There are four default exchange
types defined by the AMQP standard, and vendors can define custom
types (so see your vendors manual for details).
These are the default exchange types defined by AMQP/0.8:
* Direct exchange
Matches if the routing key property of the message and
2010-10-27 07:17:37 +00:00
the `routing_key` attribute of the consumer are identical.
2010-06-23 10:08:39 +00:00
* Fan-out exchange
Always matches, even if the binding does not have a routing
key.
* Topic exchange
Matches the routing key property of the message by a primitive
pattern matching scheme. The message routing key then consists
2010-10-27 07:17:37 +00:00
of words separated by dots (`"."` , like domain names), and
two special characters are available; star (`"*"` ) and hash
(`"#"` ). The star matches any word, and the hash matches
zero or more words. For example `"*.stock.#"` matches the
routing keys `"usd.stock"` and `"eur.stock.db"` but not
`"stock.nasdaq"` .
2010-06-23 10:08:39 +00:00
2016-04-11 20:02:34 +00:00
Installation
============
You can install `Kombu` either via the Python Package Index (PyPI)
or from source.
To install using `pip` ,:
2016-10-15 00:55:10 +00:00
2016-04-11 20:02:34 +00:00
::
$ pip install kombu
To install using `easy_install` ,:
2016-10-15 00:55:10 +00:00
2016-04-11 20:02:34 +00:00
::
$ easy_install kombu
If you have downloaded a source tarball you can install it
by doing the following,:
2016-10-15 00:55:10 +00:00
2016-04-11 20:02:34 +00:00
::
$ python setup.py build
# python setup.py install # as root
2010-06-23 10:08:39 +00:00
Getting Help
============
Mailing list
------------
2018-04-09 18:25:44 +00:00
Join the `celery-users`_ mailing list.
2010-06-23 10:08:39 +00:00
2021-11-08 00:12:33 +00:00
.. _`kombu forum`: https://github.com/celery/kombu/discussions
2010-06-23 10:08:39 +00:00
Bug tracker
===========
If you have any suggestions, bug reports or annoyances please report them
2017-05-30 13:53:40 +00:00
to our issue tracker at https://github.com/celery/kombu/issues/
2010-06-23 10:08:39 +00:00
Contributing
============
2017-05-30 13:53:40 +00:00
Development of `Kombu` happens at Github: https://github.com/celery/kombu
2010-06-23 10:08:39 +00:00
You are highly encouraged to participate in the development. If you don't
like Github (for some reason) you're welcome to send regular patches.
License
=======
2010-11-11 15:16:07 +00:00
This software is licensed under the `New BSD License` . See the `LICENSE`
2010-06-23 10:08:39 +00:00
file in the top distribution directory for the full license text.
2013-11-15 13:11:39 +00:00
2016-04-11 20:02:34 +00:00
2022-12-29 11:15:07 +00:00
.. |build-status| image :: https://github.com/celery/kombu/actions/workflows/ci.yaml/badge.svg
2016-04-11 20:02:34 +00:00
:alt: Build status
2022-12-29 11:15:07 +00:00
:target: https://github.com/celery/kombu/actions/workflows/ci.yml
2016-04-11 20:02:34 +00:00
2022-12-29 11:15:07 +00:00
.. |coverage| image :: https://codecov.io/github/celery/kombu/coverage.svg?branch=main
:target: https://codecov.io/github/celery/kombu?branch=main
2016-04-11 20:02:34 +00:00
2016-08-18 23:18:25 +00:00
.. |license| image :: https://img.shields.io/pypi/l/kombu.svg
:alt: BSD License
:target: https://opensource.org/licenses/BSD-3-Clause
.. |wheel| image :: https://img.shields.io/pypi/wheel/kombu.svg
:alt: Kombu can be installed via wheel
2018-06-10 10:40:04 +00:00
:target: https://pypi.org/project/kombu/
2016-08-18 23:18:25 +00:00
.. |pyversion| image :: https://img.shields.io/pypi/pyversions/kombu.svg
:alt: Supported Python versions.
2018-06-10 10:40:04 +00:00
:target: https://pypi.org/project/kombu/
2016-08-18 23:18:25 +00:00
.. |pyimp| image :: https://img.shields.io/pypi/implementation/kombu.svg
2019-06-06 04:15:12 +00:00
:alt: Support Python implementations.
:target: https://pypi.org/project/kombu/
2020-10-08 21:00:26 +00:00
.. |downloads| image :: https://pepy.tech/badge/kombu
:target: https://pepy.tech/project/kombu
2021-11-02 16:36:02 +00:00
2019-12-03 01:20:20 +00:00
kombu as part of the Tidelift Subscription
2021-11-02 16:36:02 +00:00
=======
2019-12-03 01:20:20 +00:00
The maintainers of kombu and thousands of other packages are working with Tidelift to deliver commercial support and maintenance for the open source dependencies you use to build your applications. Save time, reduce risk, and improve code health, while paying the maintainers of the exact dependencies you use. [Learn more.](https://tidelift.com/subscription/pkg/pypi-kombu?utm_source=pypi-kombu&utm_medium=referral&utm_campaign=readme&utm_term=repo)
2021-11-02 16:36:02 +00:00
2016-04-11 20:02:34 +00:00
--
2019-06-06 04:15:12 +00:00