Go to file
Ask Solem 5fec367b97 OS X -> macOS 2016-06-13 18:52:02 -07:00
celery OS X -> macOS 2016-06-13 18:52:02 -07:00
docs OS X -> macOS 2016-06-13 18:52:02 -07:00
examples an URL -> a URL 2016-05-12 18:51:19 -07:00
extra OS X -> macOS 2016-06-13 18:52:02 -07:00
funtests Removes funtests/suite/test_basic, replaced by Cyanide 2016-06-13 16:09:29 -07:00
requirements Now depends case 1.2 2016-06-13 17:04:31 -07:00
.coveragerc Enable coverage for cassandra. 2016-02-15 10:20:21 +02:00
.editorconfig Dist things 2016-04-08 19:08:15 -07:00
.gitignore Use sphinx_celery to manage Sphinx 2016-04-07 17:23:46 -07:00
.travis.yml [reqs][test] now depends on case 1.1.2 2016-04-08 23:50:19 -07:00
CONTRIBUTING.rst OS X -> macOS 2016-06-13 18:52:02 -07:00
CONTRIBUTORS.txt update the config with preconfig as non-defaults so they will be pickled 2016-05-23 14:46:27 -07:00
Changelog Master is now 4.0.0b1 and in feature-freeze 2015-10-29 18:42:10 -07:00
LICENSE Updates copyright year 2016-01-12 11:47:24 -08:00
MANIFEST.in OS X -> macOS 2016-06-13 18:52:02 -07:00
Makefile flakes 2016-05-26 17:28:13 -07:00
README.rst [docs] Spelling stuff completed 2016-04-13 17:26:07 -07:00
TODO Use https for github and wikipedia links 2016-03-20 22:43:38 +01:00
appveyor.yml [appveyor] must install requirements/dev.txt 2015-12-02 13:21:39 -08:00
setup.cfg Use sphinx_celery to manage Sphinx 2016-04-07 17:23:46 -07:00
setup.py [backends] Add Consul.io Key/Value store as a backend 2016-05-27 15:27:20 -07:00
tox.ini flakes 2016-05-26 17:28:13 -07:00


celery - Distributed Task Queue


Build status coverage Bitdeli badge


4.0.0rc2 (0today8)








task queue, job queue, asynchronous, async, rabbitmq, amqp, redis, python, webhooks, queue, distributed


What is a Task Queue?

Task queues are used as a mechanism to distribute work across threads or machines.

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, and a PHP client.

Language interoperability can also be achieved by using webhooks.

What do I need?

Celery version 3.0 runs on,

  • Python (2.7, 3.4, 3.5)
  • PyPy (1.8, 1.9)
  • Jython (2.5, 2.7).

This is the last version to support Python 2.5, and from Celery 3.1, Python 2.6 or later is required. The last version to support Python 2.4 was Celery series 2.2.

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 across datacenters.

Get Started

If this is the first time you're trying to use Celery, or you are new to Celery 3.0 coming from previous versions then you should read our getting started tutorials:

Celery is... ==========

  • Simple

    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, including a mailing-list and and an IRC channel.

    Here's one of the simplest applications you can make:

    from celery import Celery
    app = Celery('hello', broker='amqp://guest@localhost//')
    def hello():
        return 'hello world'
  • Highly Available

    Workers and clients will automatically retry in the event of connection loss or failure, and some brokers support HA in way of Master/Master or Master/Slave replication.

  • Fast

    A single Celery process can process millions of tasks a minute, with sub-millisecond round-trip latency (using RabbitMQ, py-librabbitmq, and optimized settings).

  • Flexible

    Almost every part of Celery can be extended or used on its own, Custom pool implementations, serializers, compression schemes, logging, schedulers, consumers, producers, autoscalers, broker transports and much more.

It supports... ============

  • Message Transports

  • Concurrency

  • Result Stores

    • AMQP, Redis
    • memcached, MongoDB
    • SQLAlchemy, Django ORM
    • Apache Cassandra, IronCache, Elasticsearch
  • Serialization

    • pickle, json, yaml, msgpack.
    • zlib, bzip2 compression.
    • Cryptographic message signing.

Framework Integration

Celery is easy to integrate with web frameworks, some of which even have integration packages:

Django not needed
Pyramid pyramid_celery
Pylons celery-pylons
Flask not needed
web2py web2py-celery
Tornado tornado-celery

The integration packages are not strictly necessary, but they can make development easier, and sometimes they add important hooks like closing database connections at fork.


The latest documentation with user guides, tutorials and API reference is hosted at Read The Docs.


You can install Celery either via the Python Package Index (PyPI) or from source.

To install using pip,: :

$ pip install -U Celery

To install using easy_install,: :

$ easy_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 pip comand-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:



for using the auth security serializer.


for using the msgpack serializer.


for using the yaml serializer.



for using the eventlet pool.


for using the gevent pool.


for using the thread pool.

Transports and Backends


for using the librabbitmq C library.


for using Redis as a message transport or as a result backend.


for using MongoDB as a message transport (experimental), or as a result backend (supported).


for using Amazon SQS as a message transport (experimental).


for using the task_remote_tracebacks feature.


for using memcached as a result backend (using pylibmc)


for using memcached as a result backend (pure-python implementation).


for using Apache Cassandra as a result backend with DataStax driver.


for using CouchDB as a message transport (experimental).


for using Couchbase as a result backend.


for using Elasticsearch as a result backend.


for using Riak as a result backend.


for using Beanstalk as a message transport (experimental).


for using Zookeeper as a message transport.


for using ZeroMQ as a message transport (experimental).


for using SQLAlchemy as a message transport (experimental), or as a result backend (supported).


for using the Pyro4 message transport (experimental).


for using the SoftLayer Message Queue transport (experimental).

Downloading and installing from source

Download the latest version of Celery from http://pypi.python.org/pypi/celery/

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 are not currently using a virtualenv.

Using the development version

With pip

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 the Contributing section.

Getting Help

Mailing list

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 Freenode network.

Bug tracker

If you have any suggestions, bug reports or annoyances please report them to our issue tracker at https://github.com/celery/celery/issues/




Development of celery happens at GitHub: https://github.com/celery/celery

You are highly encouraged to participate in the development of 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 documentation.


This software is licensed under the New BSD License. See the LICENSE file in the top distribution directory for the full license text.