Celery v4.1.0 Documentationthe exception and traceback). Results are not enabled by default. In order to do remote procedure calls or keep track of task results in a database, you will need to configure Celery to use a result backend 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 signatures. A signature wraps the arguments and execution signatures supports the calling API: meaning that; sig.apply_async(args=(), kwargs={}, **options) Calls the signature with optional partial arguments and partial keyword arguments. Also supports partial0 码力 | 1057 页 | 1.35 MB | 1 年前3
Celery v4.1.0 Documentationthe exception and traceback). Results are not enabled by default. In order to do remote procedure calls or keep track of task results in a database, you will need to configure Celery to use a result backend 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 signatures. A signature wraps the arguments and execution signatures supports the calling API: meaning that; • sig.apply_async(args=(), kwargs={}, **options) Calls the signature with optional partial arguments and partial keyword arguments. Also supports partial0 码力 | 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 signatures supports the calling API: meaning that; sig.apply_async(args=(), kwargs={}, **options) Calls the signature with optional partial arguments and partial keyword arguments. Also supports partial already does that (see the backend argument to Celery). Let’s look at some examples: Groups A group calls a list of tasks in parallel, and it returns a special result instance that lets you inspect the results0 码力 | 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 signatures supports the calling API: meaning that; sig.apply_async(args=(), kwargs={}, **options) Calls the signature with optional partial arguments and partial keyword arguments. Also supports partial already does that (see the backend argument to Celery). Let’s look at some examples: Groups A group calls a list of tasks in parallel, and it returns a special result instance that lets you inspect the results0 码力 | 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 signatures supports the calling API: meaning that; sig.apply_async(args=(), kwargs={}, **options) Calls the signature with optional partial arguments and partial keyword arguments. Also supports partial already does that (see the backend argument to Celery). Let’s look at some examples: Groups A group calls a list of tasks in parallel, and it returns a special result instance that lets you inspect the results0 码力 | 1042 页 | 1.37 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 apply_async(args=(),kwargs={},**options) 2.2. Getting Started 31 Celery Documentation, Release 4.0.0 Calls the signature with optional partial arguments and partial keyword arguments. Also supports partial already does that (see the backend argument to Celery). Let’s look at some examples: Groups A group calls a list of tasks in parallel, and it returns a special result instance that lets you inspect the results0 码力 | 703 页 | 2.60 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 signatures supports the calling API: meaning that; • sig.apply_async(args=(), kwargs={}, **options) Calls the signature with optional partial arguments and partial keyword arguments. Also supports partial already does that (see the backend argument to Celery). Let’s look at some examples: Groups A group calls a list of tasks in parallel, and it returns a special result instance that lets you inspect the results0 码力 | 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 signatures supports the calling API: meaning that; • sig.apply_async(args=(), kwargs={}, **options) Calls the signature with optional partial arguments and partial keyword arguments. Also supports partial already does that (see the backend argument to Celery). Let’s look at some examples: Groups A group calls a list of tasks in parallel, and it returns a special result instance that lets you inspect the results0 码力 | 707 页 | 2.63 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 signatures supports the calling API: meaning that; • sig.apply_async(args=(), kwargs={}, **options) Calls the signature with optional partial arguments and partial keyword arguments. Also supports partial already does that (see the backend argument to Celery). Let’s look at some examples: Groups A group calls a list of tasks in parallel, and it returns a special result instance that lets you inspect the results0 码力 | 707 页 | 2.63 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 apply_async(args=(),kwargs={},**options) 2.2. Getting Started 31 Celery Documentation, Release 4.0.0 Calls the signature with optional partial arguments and partial keyword arguments. Also supports partial already does that (see the backend argument to Celery). Let’s look at some examples: Groups A group calls a list of tasks in parallel, and it returns a special result instance that lets you inspect the results0 码力 | 701 页 | 2.59 MB | 1 年前3
共 51 条
- 1
- 2
- 3
- 4
- 5
- 6













