.. image:: http://docs.celeryproject.org/en/latest/_images/celery-banner-small.png
|build-status| |coverage| |license| |wheel| |pyversion| |pyimp|
:Version: 4.1.0 (latentcall)
:Keywords: task, queue, job, async, rabbitmq, amqp, redis,
python, distributed, actors
What's a Task Queue?
Task queues are used as a mechanism to distribute work across threads or
A task queue's input is a unit of work, called a task, dedicated worker
processes then constantly monitor the queue for new work to perform.
Celery communicates via messages, usually using a broker
to mediate between clients and workers. To initiate a task a client puts a
message on the queue, the broker then delivers the message to a worker.
A Celery system can consist of multiple workers and brokers, giving way
to high availability and horizontal scaling.
Celery is written in Python, but the protocol can be implemented in any
language. In addition to Python there's node-celery_ for Node.js,
Language interoperability can also be achieved by using webhooks
in such a way that the client enqueues an URL to be requested by a worker.
.. node-celery: https://github.com/mher/node-celery
PHP client: https://github.com/gjedeer/celery-php
What do I need?
Celery version 4.1 runs on,
- Python (2.7, 3.4, 3.5, 3.6)
- PyPy (5.8)
This is the last version to support Python 2.7,
and from the next version (Celery 5.x) Python 3.5 or newer is required.
If you're running an older version of Python, you need to be running
an older version of Celery:
- Python 2.6: Celery series 3.1 or earlier.
- Python 2.5: Celery series 3.0 or earlier.
- Python 2.4 was Celery series 2.2 or earlier.
Celery is a project with minimal funding,
so we don't support Microsoft Windows.
Please don't open any issues related to that platform.
Celery is usually used with a message broker to send and receive messages.
The RabbitMQ, Redis transports are feature complete,
but there's also experimental support for a myriad of other solutions, including
using SQLite for local development.
Celery can run on a single machine, on multiple machines, or even
If this is the first time you're trying to use Celery, or you're
new to Celery 4.1 coming from previous versions then you should read our
getting started tutorials:
First steps with Celery_
Tutorial teaching you the bare minimum needed to get started with Celery.
A more complete overview, showing more features.
First steps with Celery:
Celery is easy to use and maintain, and does not need configuration files.
It has an active, friendly community you can talk to for support,
like at our
mailing-list_, or the IRC channel.
Here's one of the simplest applications you can make::
from celery import Celery app = Celery('hello', broker='amqp://guest@localhost//') @app.task def hello(): return 'hello world'
Workers and clients will automatically retry in the event
of connection loss or failure, and some brokers support
HA in way of Primary/Primary or Primary/Replica replication.
A single Celery process can process millions of tasks a minute,
with sub-millisecond round-trip latency (using RabbitMQ,
py-librabbitmq, and optimized settings).
Almost every part of Celery can be extended or used on its own,
Custom pool implementations, serializers, compression schemes, logging,
schedulers, consumers, producers, broker transports, and much more.
- **Message Transports** - RabbitMQ_, Redis_, Amazon SQS - **Concurrency** - Prefork, Eventlet_, gevent_, single threaded (``solo``) - **Result Stores** - AMQP, Redis - memcached - SQLAlchemy, Django ORM - Apache Cassandra, IronCache, Elasticsearch - **Serialization** - *pickle*, *json*, *yaml*, *msgpack*. - *zlib*, *bzip2* compression. - Cryptographic message signing.
.. _RabbitMQ: https://rabbitmq.com
.. _Redis: https://redis.io
.. _SQLAlchemy: http://sqlalchemy.org
Celery is easy to integrate with web frameworks, some of which even have
+--------------------+------------------------+ | `Django`_ | not needed | +--------------------+------------------------+ | `Pyramid`_ | `pyramid_celery`_ | +--------------------+------------------------+ | `Pylons`_ | `celery-pylons`_ | +--------------------+------------------------+ | `Flask`_ | not needed | +--------------------+------------------------+ | `web2py`_ | `web2py-celery`_ | +--------------------+------------------------+ | `Tornado`_ | `tornado-celery`_ | +--------------------+------------------------+
The integration packages aren't strictly necessary, but they can make
development easier, and sometimes they add important hooks like closing
database connections at
latest documentation_ is hosted at Read The Docs, containing user guides,
tutorials, and an API reference.
latest documentation: http://docs.celeryproject.org/en/latest/
You can install Celery either via the Python Package Index (PyPI)
or from source.
To install using
$ pip install -U Celery
Celery also defines a group of bundles that can be used
to install Celery and the dependencies for a given feature.
You can specify these in your requirements or on the
command-line by using brackets. Multiple bundles can be specified by
separating them by commas.
$ pip install "celery[librabbitmq]" $ pip install "celery[librabbitmq,redis,auth,msgpack]"
The following bundles are available:
:``celery[auth]``: for using the ``auth`` security serializer. :``celery[msgpack]``: for using the msgpack serializer. :``celery[yaml]``: for using the yaml serializer. Concurrency
for using the
for using the
Transports and Backends
for using the librabbitmq C library.
for using Redis as a message transport or as a result backend.
for using Amazon SQS as a message transport (experimental).
for using the
for using Memcached as a result backend (using
for using Memcached as a result backend (pure-Python implementation).
for using Apache Cassandra as a result backend with DataStax driver.
for using Couchbase as a result backend.
for using Elasticsearch as a result backend.
for using Riak as a result backend.
for using Zookeeper as a message transport.
for using SQLAlchemy as a result backend (supported).
for using the Pyro4 message transport (experimental).
for using the SoftLayer Message Queue transport (experimental).
for using the Consul.io Key/Value store as a message transport or result backend (experimental).
specifies the lowest version possible for Django support.
You should probably not use this in your requirements, it's here for informational purposes only.
Downloading and installing from source
Download the latest version of Celery from PyPI:
You can install it by doing the following,:
$ tar xvfz celery-0.0.0.tar.gz $ cd celery-0.0.0 $ python setup.py build # python setup.py install
The last command must be executed as a privileged user if
you aren't currently using a virtualenv.
Using the development version
The Celery development version also requires the development versions of ``kombu``, ``amqp``, ``billiard``, and ``vine``. You can install the latest snapshot of these using the following pip commands: :: $ pip install https://github.com/celery/celery/zipball/master#egg=celery $ pip install https://github.com/celery/billiard/zipball/master#egg=billiard $ pip install https://github.com/celery/py-amqp/zipball/master#egg=amqp $ pip install https://github.com/celery/kombu/zipball/master#egg=kombu $ pip install https://github.com/celery/vine/zipball/master#egg=vine With git
Please see the Contributing section.
For discussions about the usage, development, and future of Celery,
please join the
celery-users_ mailing list.
Come chat with us on IRC. The #celery channel is located at the
If you have any suggestions, bug reports, or annoyances please report them
to our issue tracker at https://github.com/celery/celery/issues/
celery happens at GitHub: https://github.com/celery/celery
You're highly encouraged to participate in the development
celery. If you don't like GitHub (for some reason) you're welcome
to send regular patches.
Be sure to also read the
Contributing to Celery_ section in the
Contributing to Celery:
This software is licensed under the
New BSD License. See the
file in the top distribution directory for the full license text.
.. # vim: syntax=rst expandtab tabstop=4 shiftwidth=4 shiftround
.. |build-status| image:: https://secure.travis-ci.org/celery/celery.png?branch=master
:alt: Build status
.. |coverage| image:: https://codecov.io/github/celery/celery/coverage.svg?branch=master
.. |license| image:: https://img.shields.io/pypi/l/celery.svg
:alt: BSD License
.. |wheel| image:: https://img.shields.io/pypi/wheel/celery.svg
:alt: Celery can be installed via wheel
.. |pyversion| image:: https://img.shields.io/pypi/pyversions/celery.svg
:alt: Supported Python versions.
.. |pyimp| image:: https://img.shields.io/pypi/implementation/celery.svg
:alt: Support Python implementations.