sudo rabbitmqctl stop When the server is running, you can continue reading Setting up RabbitMQ. 1.3 First steps with Celery 1.3.1 Creating a simple task In this example we are creating a simple task re-raise errors. 8 >>> result.successful() # returns True if the task didn’t end in failure. True 1.3. First steps with Celery 9 Celery Documentation, Release 1.0.6 (stable) If the task raises an exception

sudo rabbitmqctl stop When the server is running, you can continue reading Setting up RabbitMQ. 1.3 First steps with Celery • Creating a simple task • Configuration • Running the celery worker server RabbitMQ is running, and that the user/password has access to the virtual host you configured earlier. 1.3. First steps with Celery 9 Celery Documentation, Release 2.0.3 (stable) Right now we have to check

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.3 First steps with Celery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . sudo rabbitmqctl stop When the server is running, you can continue reading Setting up RabbitMQ. 1.3 First steps with Celery • Creating a simple task • Configuration • Running the celery worker server information). For a complete listing of the command line options available, do: $ celeryd --help 1.3. First steps with Celery 9 Celery Documentation, Release 2.1.4 1.3.4 Executing the task Whenever

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.3 First steps with Celery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . transport does not currently support: • Remote control commands (celeryctl, broadcast) • Authentication 1.3 First steps with Celery • Choosing your Broker • Creating a simple task • Configuration • Running modules. By convention we will call our module tasks.py, and it looks like this: file tasks.py 1.3. First steps with Celery 13 Celery Documentation, Release 2.4.7 from celery.task import task @task

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.3 First steps with Celery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . sudo rabbitmqctl stop When the server is running, you can continue reading Setting up RabbitMQ. 1.3 First steps with Celery • Creating a simple task • Configuration • Running the celery worker server information). For a complete listing of the command line options available, do: $ celeryd --help 1.3. First steps with Celery 9 Celery Documentation, Release 2.2.10 1.3.4 Executing the task Whenever

sudo rabbitmqctl stop When the server is running, you can continue reading Setting up RabbitMQ. 1.3 First steps with Celery • Creating a simple task • Configuration • Running the celery worker server information). For a complete listing of the command line options available, do: $ celeryd --help 1.3. First steps with Celery 9 Celery Documentation, Release 2.3.5 1.3.4 Executing the task Whenever

transport does not currently support: • Remote control commands (celeryctl, broadcast) • Authentication 1.3 First steps with Celery • Choosing your Broker • Creating a simple task • Configuration • Running our celeryconfig.py. 1. Configure how we communicate with the broker (RabbitMQ in this example): 1.3. First steps with Celery 13 Celery Documentation, Release 2.5.5 BROKER_URL = "amqp://guest:guest@localhost:5672//"

usage is SUPPRESS_USAGE: self.usage = None # For backwards compatibility with Optik 1.3 and earlier. elif usage.lower().startswith("usage: "): self.usage = usage[7:] AmbiguousOptionError(s, possibilities) # Some day, there might be many Option classes. As of Optik 1.3, the # preferred way to instantiate Options is indirectly, via make_option(), # which will become

usage is SUPPRESS_USAGE: self.usage = None # For backwards compatibility with Optik 1.3 and earlier. elif usage.lower().startswith("usage: "): self.usage = usage[7:] AmbiguousOptionError(s, possibilities) # Some day, there might be many Option classes. As of Optik 1.3, the # preferred way to instantiate Options is indirectly, via make_option(), # which will become

set/delete/append/remove/etc. events. The event package is now used. .. deprecated:: 1.3 The :paramref:`.AttributeImpl.extension` parameter is deprecated and will