broadcast (one-to-many), and more. Celery aims to hide the complexity of AMQP through features like Automatic routing, while still preserving the ability to go low level if that should be necessary. 14 Chapter a custom retry delay • Task options – General – Message and routing options • Task names – Automatic naming and relative imports • Decorating tasks • Task States – Result Backends * AMQP Result @task() >>> def add(x, y): ... return x + y >>> add.name ’tasks.add’ Automatic naming and relative imports Relative imports and automatic name generation does not go well together, so if you’re using relative

Documentation, Release 2.5.5 Celery aims to hide the complexity of AMQP through features like Automatic routing, while still preserving the ability to go low level if that should be necessary. 2.1.5 a custom retry delay • Task options – General – Message and routing options • Task names – Automatic naming and relative imports • Decorating tasks • Task States – Result Backends * AMQP Result @task() >>> def add(x, y): ... return x + y >>> add.name ’tasks.add’ Automatic naming and relative imports Relative imports and automatic name generation does not go well together, so if you’re using relative

and for the best performance route long-running and short-running tasks to dedicated workers (Automatic routing). If your worker hangs then please investigate what tasks are running before submitting py: @app.task def add(x, y): return x + y >>> from tasks import add >>> add.name 'tasks.add' Automatic naming and relative imports Absolute Imports The best practice for developers targeting Python the default in Python 3 so you don’t need this if you target that version. Relative imports and automatic name generation don’t go well together, so if you’re using relative imports you should set the name

and for the best performance route long-running and short-running tasks to dedicated workers (Automatic routing). If your worker hangs then please investigate what tasks are running before submitting py: @app.task def add(x, y): return x + y >>> from tasks import add >>> add.name 'tasks.add' Automatic naming and relative imports Absolute Imports The best practice for developers targeting Python the default in Python 3 so you don’t need this if you target that version. Relative imports and automatic name generation don’t go well together, so if you’re using relative imports you should set the name

and for the best performance route long-running and short-running tasks to dedicated workers (Automatic routing). If your worker hangs then please investigate what tasks are running before submitting py: @app.task def add(x, y): return x + y >>> from tasks import add >>> add.name 'tasks.add' Automatic naming and relative imports Absolute Imports The best practice for developers targeting Python the default in Python 3 so you don’t need this if you target that version. Relative imports and automatic name generation don’t go well together, so if you’re using relative imports you should set the name

and for the best performance route long-running and short-running tasks to dedicated workers (Automatic routing). If your worker hangs then please investigate what tasks are running before submitting return x + y >>> from tasks import add >>> add.name 'tasks.add' Automatic naming and relative imports Relative imports and automatic name generation don’t go well together, so if you’re using relative on the automatic naming: @task(name='proj.tasks.add') def add(x, y): return x + y Changing the automatic naming behavior New in version 4.0. There are some cases when the default automatic naming

and for the best performance route long-running and short-running tasks to dedicated workers (Automatic routing). If your worker hangs then please investigate what tasks are running before submitting return x + y >>> from tasks import add >>> add.name 'tasks.add' Automatic naming and relative imports Relative imports and automatic name generation don’t go well together, so if you’re using relative on the automatic naming: @task(name='proj.tasks.add') def add(x, y): return x + y Changing the automatic naming behavior New in version 4.0. There are some cases when the default automatic naming

and for the best performance route long-running and short-running tasks to dedicated workers (Automatic routing). If your worker hangs then please investigate what tasks are running before submitting return x + y >>> from tasks import add >>> add.name 'tasks.add' Automatic naming and relative imports Relative imports and automatic name generation don’t go well together, so if you’re using relative on the automatic naming: @task(name='proj.tasks.add') def add(x, y): return x + y Changing the automatic naming behavior New in version 4.0. There are some cases when the default automatic naming

and for the best performance route long-running and short-running tasks to dedicated workers (Automatic routing). If your worker hangs then please investigate what tasks are running before submitting py: @app.task def add(x, y): return x + y >>> from tasks import add >>> add.name 'tasks.add' Automatic naming and relative imports 2.3. User Guide 47 Celery Documentation, Release 4.0.0 Absolute Imports the default in Python 3 so you don’t need this if you target that version. Relative imports and automatic name generation don’t go well together, so if you’re using relative imports you should set the name

and for the best performance route long-running and short-running tasks to dedicated workers (Automatic routing). If your worker hangs then please investigate what tasks are running before submitting return x + y >>> from tasks import add >>> add.name 'tasks.add' Automatic naming and relative imports Relative imports and automatic name generation don’t go well together, so if you’re using relative on the automatic naming: @task(name='proj.tasks.add') def add(x, y): return x + y Changing the automatic naming behavior New in version 4.0. There are some cases when the default automatic naming