Celery v4.0.1 Documentationwant to pass the signature of a task invocation to another process or as an argument to another function, for this Celery uses something called signatures. A signature wraps the arguments and execution add> and there you see that __main__ again; whenever Celery isn’t 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 __init__(self, app): self.app = app Internally Celery uses the celery.app.app_or_default() function so that everything also works in the module-based compatibility API from celery.app import app_or_default0 码力 | 1040 页 | 1.37 MB | 1 年前3
Celery v4.0.2 Documentationwant to pass the signature of a task invocation to another process or as an argument to another function, for this Celery uses something called signatures. A signature wraps the arguments and execution add> and there you see that __main__ again; whenever Celery isn’t 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 __init__(self, app): self.app = app Internally Celery uses the celery.app.app_or_default() function so that everything also works in the module-based compatibility API from celery.app import app_or_default0 码力 | 1042 页 | 1.37 MB | 1 年前3
Celery 4.0 Documentationwant to pass the signature of a task invocation to another process or as an argument to another function, for this Celery uses something called signatures. A signature wraps the arguments and execution add> and there you see that __main__ again; whenever Celery isn’t 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 __init__(self, app): self.app = app Internally Celery uses the celery.app.app_or_default() function so that everything also works in the module-based compatibility API from celery.app import app_or_default0 码力 | 1042 页 | 1.37 MB | 1 年前3
Celery 2.1 Documentationclasses that inherits from the Task class. In this example we’re using a decorator that wraps the add function in an appropriate class for us automatically. See also: The full documentation on how to create 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 Celery Documentation, Release 2.1.4 For convenience there is a shortcut decorator that turns any function into a task: from celery.decorators import task from django.contrib.auth import User @task def0 码力 | 285 页 | 1.19 MB | 1 年前3
Celery v4.1.0 Documentationwant to pass the signature of a task invocation to another process or as an argument to another function, for this Celery uses something called signatures. A signature wraps the arguments and execution add> and there you see that __main__ again; whenever Celery isn’t 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 __init__(self, app): self.app = app Internally Celery uses the celery.app.app_or_default() function so that everything also works in the module-based compatibility API from celery.app import app_or_default0 码力 | 1057 页 | 1.35 MB | 1 年前3
Celery 3.0 Documentationwant to pass the signature of a task invocation to another process or as an argument to another function, for this Celery uses something called signatures. A signature wraps the arguments and execution add> and there you see that __main__ again; whenever Celery isn’t 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 def __init__(self, app): self.app = app Internally Celery uses the celery.app.app_or_default() function so that everything also works in the module-based compatibility API from celery.app import app_or_default0 码力 | 703 页 | 2.60 MB | 1 年前3
Celery v4.0.0 Documentationwant to pass the signature of a task invocation to another process or as an argument to another function, for this Celery uses something called signatures. A signature wraps the arguments and execution add> and there you see that __main__ again; whenever Celery isn’t 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 def __init__(self, app): self.app = app Internally Celery uses the celery.app.app_or_default() function so that everything also works in the module-based compatibility API from celery.app import app_or_default0 码力 | 701 页 | 2.59 MB | 1 年前3
Celery v4.1.0 Documentationwant to pass the signature of a task invocation to another process or as an argument to another function, for this Celery uses something called signatures. A signature wraps the arguments and execution add> and there you see that __main__ again; whenever Celery isn’t 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 def __init__(self, app): self.app = app Internally Celery uses the celery.app.app_or_default() function so that everything also works in the module-based compatibility API from celery.app import app_or_default0 码力 | 714 页 | 2.63 MB | 1 年前3
Celery v4.0.1 Documentationwant to pass the signature of a task invocation to another process or as an argument to another function, for this Celery uses something called signatures. A signature wraps the arguments and execution add> and there you see that __main__ again; whenever Celery isn’t 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 def __init__(self, app): self.app = app Internally Celery uses the celery.app.app_or_default() function so that everything also works in the module-based compatibility API from celery.app import app_or_default0 码力 | 705 页 | 2.63 MB | 1 年前3
Celery 4.0 Documentationwant to pass the signature of a task invocation to another process or as an argument to another function, for this Celery uses something called signatures. A signature wraps the arguments and execution add> and there you see that __main__ again; whenever Celery isn’t 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 def __init__(self, app): self.app = app Internally Celery uses the celery.app.app_or_default() function so that everything also works in the module-based compatibility API from celery.app import app_or_default0 码力 | 707 页 | 2.63 MB | 1 年前3
共 51 条
- 1
- 2
- 3
- 4
- 5
- 6













