Documentation, Release 2.3.5 2.2.1 Basics A task is a class that encapsulates a function and its execution options. Given a function create_user‘, that takes two arguments: username and password, you can create registered, but any task inheriting from it will be. When tasks are sent, we don’t send any actual function code, just the name of the task to execute. When the worker then receives the message it can look and the shortcut: delay(). delay is simple and convenient, as it looks like calling a regular function: Task.delay(arg1, arg2, kwarg1="x", kwarg2="y") The same using apply_async is written like this:

see the API reference. 2.2.1 Basics A task is a class that encapsulates a function and its execution options. Given a function create_user‘, that takes two arguments: username and password, you can create registered, but any task inheriting from it will be. When tasks are sent, we don’t send any actual function code, just the name of the task to execute. When the worker then receives the message it can look and the shortcut: delay(). delay is simple and convenient, as it looks like calling a regular function: Task.delay(arg1, arg2, kwarg1="x", kwarg2="y") The same using apply_async is written like this:

please see the API reference. Basics A task is a class that encapsulates a function and its execution options. Given a function create_user`, that takes two arguments: username and password, you can create registered, but any task inheriting from it will be. When tasks are sent, we don’t send any actual function code, just the name of the task to execute. When the worker then receives the message it can look and the shortcut: delay(). delay is simple and convenient, as it looks like calling a regular function: Task.delay(arg1, arg2, kwarg1="x", kwarg2="y") The same using apply_async is written like this:

see the API reference. 2.2.1 Basics A task is a class that encapsulates a function and its execution options. Given a function create_user‘, that takes two arguments: username and password, you can create registered, but any task inheriting from it will be. When tasks are sent, we don’t send any actual function code, just the name of the task to execute. When the worker then receives the message it can look and the shortcut: delay(). delay is simple and convenient, as it looks like calling a regular function: 2.3. Executing Tasks 37 Celery Documentation, Release 2.5.5 Task.delay(arg1, arg2, kwarg1="x"

please see the API reference. Basics A task is a class that encapsulates a function and its execution options. Given a function create_user`, that takes two arguments: username and password, you can create registered, but any task inheriting from it will be. When tasks are sent, we don’t send any actual function code, just the name of the task to execute. When the worker then receives the message it can look and the shortcut: delay(). delay is simple and convenient, as it looks like calling a regular function: Task.delay(arg1, arg2, kwarg1="x", kwarg2="y") The same using apply_async is written like this:

please see the API reference. Basics A task is a class that encapsulates a function and its execution options. Given a function create_user`, that takes two arguments: username and password, you can create registered, but any task inheriting from it will be. When tasks are sent, we don’t send any actual function code, just the name of the task to execute. When the worker then receives the message it can look and the shortcut: delay(). delay is simple and convenient, as it looks like calling a regular function: Task.delay(arg1, arg2, kwarg1="x", kwarg2="y") The same using apply_async is written like this:

see the API reference. 2.2.1 Basics A task is a class that encapsulates a function and its execution options. Given a function create_user‘, that takes two arguments: username and password, you can create registered, but any task inheriting from it will be. When tasks are sent, we don’t send any actual function code, just the name of the task to execute. When the worker then receives the message it can look and the shortcut: delay(). delay is simple and convenient, as it looks like calling a regular function: Task.delay(arg1, arg2, kwarg1="x", kwarg2="y") The same using apply_async is written like this:

please see the API reference. Basics A task is a class that encapsulates a function and its execution options. Given a function create_user`, that takes two arguments: username and password, you can create registered, but any task inheriting from it will be. When tasks are sent, we don’t send any actual function code, just the name of the task to execute. When the worker then receives the message it can look and the shortcut: delay(). delay is simple and convenient, as it looks like calling a regular function: Task.delay(arg1, arg2, kwarg1="x", kwarg2="y") The same using apply_async is written like this:

want to pass the signature of a task invocation to another process or as an argument to another function, for this Celery uses something called subtasks. A subtask wraps the arguments and execution options to see what the workers are doing: $ celery -A proj events --dump or you can start the curses interface: $ celery -A proj events when you’re finished monitoring you can disable events again: $ celery add> and there you see that __main__ again; whenever Celery is not able to detect what module the function belongs to, it uses the main module name to generate the beginning of the task name. This is only

want to pass the signature of a task invocation to another process or as an argument to another function, for this Celery uses something called subtasks. A subtask wraps the arguments and execution options to see what the workers are doing: $ celery -A proj events --dump or you can start the curses interface: $ celery -A proj events when you’re finished monitoring you can disable events again: $ celery add> and there you see that __main__ again; whenever Celery is not able to detect what module the function belongs to, it uses the main module name to generate the beginning of the task name. This is only