Celery 3.0 Documentationproject with minimal funding, so we don’t support Microsoft Windows. Please don’t open any issues related to that platform. Celery requires a message transport to send and receive messages. The RabbitMQ Workers will receive all task related events by default. To avoid this you must set the fanout_patterns fanout option so that the workers may only subscribe to worker related events: app.conf.broker_transport_options must always return the same output. Task Request app.Task.request contains information and state related to the currently executing task. The request defines the following attributes: id The unique id0 码力 | 703 页 | 2.60 MB | 1 年前3
Celery v4.0.1 Documentationproject with minimal funding, so we don’t support Microsoft Windows. Please don’t open any issues related to that platform. Redis broker transports are feature complete, but there’s also support for a myriad Workers will receive all task related events by default. To avoid this you must set the fanout_patterns fanout option so that the workers may only subscribe to worker related events: app.conf.broker_transport_options must always return the same output. Task Request app.Task.request contains information and state related to the currently executing task. The request defines the following attributes: id: The unique id0 码力 | 1040 页 | 1.37 MB | 1 年前3
Celery v4.0.2 Documentationproject with minimal funding, so we don’t support Microsoft Windows. Please don’t open any issues related to that platform. Redis broker transports are feature complete, but there’s also support for a myriad Workers will receive all task related events by default. To avoid this you must set the fanout_patterns fanout option so that the workers may only subscribe to worker related events: app.conf.broker_transport_options must always return the same output. Task Request app.Task.request contains information and state related to the currently executing task. The request defines the following attributes: id: The unique id0 码力 | 1042 页 | 1.37 MB | 1 年前3
Celery v4.1.0 Documentationproject with minimal funding, so we don’t support Microsoft Windows. Please don’t open any issues related to that platform. 6 Chapter 2. Contents Celery Documentation, Release 4.1.0 Celery requires a Workers will receive all task related events by default. To avoid this you must set the fanout_patterns fanout option so that the workers may only subscribe to worker related events: app.conf.broker_transport_options Celery Documentation, Release 4.1.0 Task Request app.Task.request contains information and state related to the currently executing task. The request defines the following attributes: id The unique id0 码力 | 714 页 | 2.63 MB | 1 年前3
Celery v4.0.1 Documentationproject with minimal funding, so we don’t support Microsoft Windows. Please don’t open any issues related to that platform. 6 Chapter 2. Contents Celery Documentation, Release 4.0.1 Celery requires a Workers will receive all task related events by default. To avoid this you must set the fanout_patterns fanout option so that the workers may only subscribe to worker related events: app.conf.broker_transport_options Celery Documentation, Release 4.0.1 Task Request app.Task.request contains information and state related to the currently executing task. The request defines the following attributes: id The unique id0 码力 | 705 页 | 2.63 MB | 1 年前3
Celery v4.1.0 Documentationproject with minimal funding, so we don’t support Microsoft Windows. Please don’t open any issues related to that platform. Redis broker transports are feature complete, but there’s also support for a myriad Workers will receive all task related events by default. To avoid this you must set the fanout_patterns fanout option so that the workers may only subscribe to worker related events: app.conf.broker_transport_options must always return the same output. Task Request app.Task.request contains information and state related to the currently executing task. The request defines the following attributes: id: The unique id0 码力 | 1057 页 | 1.35 MB | 1 年前3
Celery v4.0.0 Documentationproject with minimal funding, so we don’t support Microsoft Windows. Please don’t open any issues related to that platform. Celery requires a message transport to send and receive messages. The RabbitMQ Workers will receive all task related events by default. To avoid this you must set the fanout_patterns fanout option so that the workers may only subscribe to worker related events: app.conf.broker_transport_options must always return the same output. Task Request app.Task.request contains information and state related to the currently executing task. The request defines the following attributes: id The unique id0 码力 | 701 页 | 2.59 MB | 1 年前3
Celery 4.0 Documentationproject with minimal funding, so we don’t support Microsoft Windows. Please don’t open any issues related to that platform. 6 Chapter 2. Contents Celery Documentation, Release 4.0.2 Celery requires a Workers will receive all task related events by default. To avoid this you must set the fanout_patterns fanout option so that the workers may only subscribe to worker related events: app.conf.broker_transport_options Celery Documentation, Release 4.0.2 Task Request app.Task.request contains information and state related to the currently executing task. The request defines the following attributes: id The unique id0 码力 | 707 页 | 2.63 MB | 1 年前3
Celery v4.0.2 Documentationproject with minimal funding, so we don’t support Microsoft Windows. Please don’t open any issues related to that platform. 6 Chapter 2. Contents Celery Documentation, Release 4.0.2 Celery requires a Workers will receive all task related events by default. To avoid this you must set the fanout_patterns fanout option so that the workers may only subscribe to worker related events: app.conf.broker_transport_options Celery Documentation, Release 4.0.2 Task Request app.Task.request contains information and state related to the currently executing task. The request defines the following attributes: id The unique id0 码力 | 707 页 | 2.63 MB | 1 年前3
Celery 4.0 Documentationproject with minimal funding, so we don’t support Microsoft Windows. Please don’t open any issues related to that platform. Redis broker transports are feature complete, but there’s also support for a myriad Workers will receive all task related events by default. To avoid this you must set the fanout_patterns fanout option so that the workers may only subscribe to worker related events: app.conf.broker_transport_options must always return the same output. Task Request app.Task.request contains information and state related to the currently executing task. The request defines the following attributes: id: The unique id0 码力 | 1042 页 | 1.37 MB | 1 年前3
共 51 条
- 1
- 2
- 3
- 4
- 5
- 6













