Celery v5.0.1 Documentationmethod. This is a handy shortcut to the apply_async() method that gives greater control of the task execution (see Calling Tasks): >>> from tasks import add >>> add.delay(4, 4) The task has now been processed another method called apply_async(): >>> add.apply_async((2, 2)) The latter enables you to specify execution options like the time to run (countdown), the queue it should be sent to, and so on: >>> add.apply_async((2 apply_async methods return an AsyncResult instance, which can be used to keep track of the tasks execution state. But for this you need to enable a result backend so that the state can be stored somewhere0 码力 | 2313 页 | 2.13 MB | 1 年前3
Celery v5.0.2 Documentationmethod. This is a handy shortcut to the apply_async() method that gives greater control of the task execution (see Calling Tasks): >>> from tasks import add >>> add.delay(4, 4) The task has now been processed another method called apply_async(): >>> add.apply_async((2, 2)) The latter enables you to specify execution options like the time to run (countdown), the queue it should be sent to, and so on: >>> add.apply_async((2 apply_async methods return an AsyncResult instance, which can be used to keep track of the tasks execution state. But for this you need to enable a result backend so that the state can be stored somewhere0 码力 | 2313 页 | 2.14 MB | 1 年前3
Celery v5.0.0 Documentationmethod. This is a handy shortcut to the apply_async() method that gives greater control of the task execution (see Calling Tasks): >>> from tasks import add >>> add.delay(4, 4) The task has now been processed another method called apply_async(): >>> add.apply_async((2, 2)) The latter enables you to specify execution options like the time to run (countdown), the queue it should be sent to, and so on: >>> add.apply_async((2 apply_async methods return an AsyncResult instance, which can be used to keep track of the tasks execution state. But for this you need to enable a result backend so that the state can be stored somewhere0 码力 | 2309 页 | 2.13 MB | 1 年前3
Celery v5.0.5 Documentationmethod. This is a handy shortcut to the apply_async() method that gives greater control of the task execution (see Calling Tasks): >>> from tasks import add >>> add.delay(4, 4) The task has now been processed another method called apply_async(): >>> add.apply_async((2, 2)) The latter enables you to specify execution options like the time to run (countdown), the queue it should be sent to, and so on: >>> add.apply_async((2 apply_async methods return an AsyncResult instance, which can be used to keep track of the tasks execution state. But for this you need to enable a result backend so that the state can be stored somewhere0 码力 | 2315 页 | 2.14 MB | 1 年前3
Celery 2.1 Documentationdistributed message passing. It is focused on real-time operation, but supports scheduling as well. The execution units, called tasks, are executed concurrently on one or more worker nodes. Tasks can execute asyn- fact. UUID Every task has an UUID (Universally Unique Identifier), which is the task id used to query task status and return value. Retries Tasks can be retried if they fail, with configurable maximum been executed, and even retrieve the results in order. Progress bars, anyone? Made for Web You can query status and results via URLs, enabling the ability to poll task status using Ajax. Error e-mails0 码力 | 285 页 | 1.19 MB | 1 年前3
Celery 2.1 Documentationdistributed message passing. It is focused on real-time operation, but supports scheduling as well. The execution units, called tasks, are executed concurrently on one or more worker nodes. Tasks can execute asynchronously fact. UUID Every task has an UUID (Universally Unique Identifier), which is the task id used to query task status and return value. Retries Tasks can be retried if they fail, with configurable maximum been executed, and even retrieve the results in order. Progress bars, anyone? Made for Web You can query status and results via URLs, enabling the ability to poll task status using Ajax. Error e-mails Can0 码力 | 463 页 | 861.69 KB | 1 年前3
Celery 3.0 Documentationmethod. This is a handy shortcut to the apply_async() method that gives greater control of the task execution (see Calling Tasks): >>> from tasks import add >>> add.delay(4, 4) The task has now been processed another method called apply_async(): >>> add.apply_async((2, 2)) The latter enables you to specify execution options like the time to run (countdown), the queue it should be sent to, and so on: >>> add.apply_async((2 apply_async methods return an AsyncResult instance, that can be used to keep track of the tasks execution state. But for this you need to enable a result backend so that the state can be stored somewhere0 码力 | 2110 页 | 2.23 MB | 1 年前3
Celery v4.0.0 Documentationmethod. This is a handy shortcut to the apply_async() method that gives greater control of the task execution (see Calling Tasks): >>> from tasks import add >>> add.delay(4, 4) The task has now been processed another method called apply_async(): >>> add.apply_async((2, 2)) The latter enables you to specify execution options like the time to run (countdown), the queue it should be sent to, and so on: >>> add.apply_async((2 apply_async methods return an AsyncResult instance, that can be used to keep track of the tasks execution state. But for this you need to enable a result backend so that the state can be stored somewhere0 码力 | 2106 页 | 2.23 MB | 1 年前3
Celery 2.3 Documentationdistributed message passing. It is focused on real-time operation, but supports scheduling as well. The execution units, called tasks, are executed concurrently on one or more worker nodes using multiprocessing fact. UUID Every task has an UUID (Universally Unique Identifier), which is the task id used to query task status and return value. Retries Tasks can be retried if they fail, with configurable maximum been executed, and even retrieve the results in order. Progress bars, anyone? Made for Web You can query status and results via URLs, enabling the ability to poll task status using Ajax. Error Emails Can0 码力 | 334 页 | 1.25 MB | 1 年前3
Celery 2.2 Documentationdistributed message passing. It is focused on real-time operation, but supports scheduling as well. The execution units, called tasks, are executed concurrently on one or more worker nodes using multiprocessing fact. UUID Every task has an UUID (Universally Unique Identifier), which is the task id used to query task status and return value. Retries Tasks can be retried if they fail, with configurable maximum been executed, and even retrieve the results in order. Progress bars, anyone? Made for Web You can query status and results via URLs, enabling the ability to poll task status using Ajax. Error E-mails0 码力 | 314 页 | 1.26 MB | 1 年前3
共 51 条
- 1
- 2
- 3
- 4
- 5
- 6













