Celery 2.1 DocumentationX. Note: If you’re getting nodedown errors after installing and using rabbitmqctl then this blog post can help you identify the source of the problem: http://somic.org/2009/02/19/on-rabbitmqctl-and-badrpcnodedown/ object returned. The AsyncResult lets us check the state of the task, wait for the task to finish, get its return value or excep- tion/traceback if the task failed, and more. Let’s execute the task again processing. False >>> result.result # task is not ready, so no return value yet. None >>> result.get() # Waits until the task is done and returns the retval. 8 >>> result.result # direct access to result0 码力 | 285 页 | 1.19 MB | 1 年前3
Celery 2.1 DocumentationX. Note If you’re getting nodedown errors after installing and using rabbitmqctl then this blog post can help you identify the source of the problem: http://somic.org/2009/02/19/on-rabbitmqctl-and-badrpcnodedown/ object returned. The AsyncResult lets us check the state of the task, wait for the task to finish, get its return value or exception/traceback if the task failed, and more. Let’s execute the task again processing. False >>> result.result # task is not ready, so no return value yet. None >>> result.get() # Waits until the task is done and returns the retval. 8 >>> result.result # direct access to0 码力 | 463 页 | 861.69 KB | 1 年前3
Celery 1.0 Documentationreturned by delay. The AsyncResult lets us find the state of the task, wait for the task to finish and get its return value (or exception if the task failed). So, let’s execute the task again, but this time finished processing. False >>> result.result # task is not ready, so no return value yet. None >>> result.get() # Waits until the task is done and returns the retval. 8 >>> result.result # direct access to result returned by delay. The AsyncResult lets us find the state of the task, wait for the task to finish and get its return value (or exception if the task failed). So, let’s execute the task again, but this time0 码力 | 123 页 | 400.69 KB | 1 年前3
Celery 2.3 DocumentationX. Note: If you’re getting nodedown errors after installing and using rabbitmqctl then this blog post can help you identify the source of the problem: http://somic.org/2009/02/19/on-rabbitmqctl-and-badrpcnodedown/ result store the AsyncResult enables you to check the state of the task, wait for the task to finish, get its return value or exception/traceback if the task failed, and more. Keeping Results If you want processing. False >>> result.result # task is not ready, so no return value yet. None >>> result.get() # Waits until the task is done and returns the retval. 8 >>> result.result # direct access to result0 码力 | 334 页 | 1.25 MB | 1 年前3
Celery 1.0 Documentationreturned by delay. The AsyncResult lets us find the state of the task, wait for the task to finish and get its return value (or exception if the task failed). So, let’s execute the task again, but this time processing. False >>> result.result # task is not ready, so no return value yet. None >>> result.get() # Waits until the task is done and returns the retval. 8 >>> result.result # direct access to returned by delay. The AsyncResult lets us find the state of the task, wait for the task to finish and get its return value (or exception if the task failed). So, let’s execute the task again, but this time0 码力 | 221 页 | 283.64 KB | 1 年前3
Celery 2.2 DocumentationX. Note: If you’re getting nodedown errors after installing and using rabbitmqctl then this blog post can help you identify the source of the problem: http://somic.org/2009/02/19/on-rabbitmqctl-and-badrpcnodedown/ object returned. The AsyncResult lets us check the state of the task, wait for the task to finish, get its return value or excep- tion/traceback if the task failed, and more. Let’s execute the task again processing. False >>> result.result # task is not ready, so no return value yet. None >>> result.get() # Waits until the task is done and returns the retval. 8 >>> result.result # direct access to result0 码力 | 314 页 | 1.26 MB | 1 年前3
Celery 2.2 DocumentationX. Note If you’re getting nodedown errors after installing and using rabbitmqctl then this blog post can help you identify the source of the problem: http://somic.org/2009/02/19/on-rabbitmqctl-and-badrpcnodedown/ object returned. The AsyncResult lets us check the state of the task, wait for the task to finish, get its return value or exception/traceback if the task failed, and more. Let’s execute the task again processing. False >>> result.result # task is not ready, so no return value yet. None >>> result.get() # Waits until the task is done and returns the retval. 8 >>> result.result # direct access to0 码力 | 505 页 | 878.66 KB | 1 年前3
Celery 2.3 DocumentationX. Note If you’re getting nodedown errors after installing and using rabbitmqctl then this blog post can help you identify the source of the problem: http://somic.org/2009/02/19/on-rabbitmqctl-and-badrpcnodedown/ result store the AsyncResult enables you to check the state of the task, wait for the task to finish, get its return value or exception/traceback if the task failed, and more. Keeping Results If you want processing. False >>> result.result # task is not ready, so no return value yet. None >>> result.get() # Waits until the task is done and returns the retval. 8 >>> result.result # direct access to0 码力 | 530 页 | 900.64 KB | 1 年前3
Celery 2.5 DocumentationX. Note: If you’re getting nodedown errors after installing and using rabbitmqctl then this blog post can help you identify the source of the problem: http://somic.org/2009/02/19/on-rabbitmqctl-and-badrpcnodedown/ result store the AsyncResult enables you to check the state of the task, wait for the task to finish, get its return value or exception/traceback if the task failed, and more. Keeping Results If you want processing. False >>> result.result # task is not ready, so no return value yet. None >>> result.get() # Waits until the task is done and returns the retval. 8 >>> result.result # direct access to result0 码力 | 400 页 | 1.40 MB | 1 年前3
Celery 2.0 Documentationreturned by delay(). The AsyncResult lets us find the state of the task, wait for the task to finish, get its return value (or exception if the task failed), and more. So, let’s execute the task again, but processing. False >>> result.result # task is not ready, so no return value yet. None >>> result.get() # Waits until the task is done and returns the retval. 8 >>> result.result # direct access to result right thing. The current default keyword arguments are: • logfile The log file, can be passed on to get_logger() to gain access to the workers log file. See Logging. • loglevel The loglevel used. • task_id0 码力 | 165 页 | 492.43 KB | 1 年前3
共 51 条
- 1
- 2
- 3
- 4
- 5
- 6













