Celery v5.0.1 DocumentationStartStopStep): requires = {'celery.worker.consumer.connection:Connection'} event_dispatcher A app.events.Dispatcher object that can be used to send events. A consumer bootstep must require the Events app.events. Dispatcher[source] Receiver[source] State[source] default_dispatcher(hostname=None, enabled=True, buffer_while_offline=False)[source] dispatcher_cls = 'celery.events.dispatcher:EventDispatcher' version of Celery (5.0). For development docs, go here. celery.events Monitoring Event Receiver+Dispatcher. Events is a stream of messages sent for certain actions occurring in the worker (and clients0 码力 | 2313 页 | 2.13 MB | 1 年前3
Celery v5.0.2 DocumentationStartStopStep): requires = {'celery.worker.consumer.connection:Connection'} event_dispatcher A app.events.Dispatcher object that can be used to send events. A consumer bootstep must require the Events app.events. Dispatcher[source] Receiver[source] State[source] default_dispatcher(hostname=None, enabled=True, buffer_while_offline=False)[source] dispatcher_cls = 'celery.events.dispatcher:EventDispatcher' version of Celery (5.0). For development docs, go here. celery.events Monitoring Event Receiver+Dispatcher. Events is a stream of messages sent for certain actions occurring in the worker (and clients0 码力 | 2313 页 | 2.14 MB | 1 年前3
Celery v5.0.0 DocumentationStartStopStep): requires = {'celery.worker.consumer.connection:Connection'} event_dispatcher A app.events.Dispatcher object that can be used to send events. A consumer bootstep must require the Events app.events. Dispatcher[source] Receiver[source] State[source] default_dispatcher(hostname=None, enabled=True, buffer_while_offline=False)[source] dispatcher_cls = 'celery.events.dispatcher:EventDispatcher' version of Celery (5.0). For development docs, go here. celery.events Monitoring Event Receiver+Dispatcher. Events is a stream of messages sent for certain actions occurring in the worker (and clients0 码力 | 2309 页 | 2.13 MB | 1 年前3
Celery v5.0.5 DocumentationStartStopStep): requires = {'celery.worker.consumer.connection:Connection'} event_dispatcher A app.events.Dispatcher object that can be used to send events. A consumer bootstep must require the Events app.events. Dispatcher[source] Receiver[source] State[source] default_dispatcher(hostname=None, enabled=True, buffer_while_offline=False)[source] dispatcher_cls = 'celery.events.dispatcher:EventDispatcher' version of Celery (5.0). For development docs, go here. celery.events Monitoring Event Receiver+Dispatcher. Events is a stream of messages sent for certain actions occurring in the worker (and clients0 码力 | 2315 页 | 2.14 MB | 1 年前3
Celery 3.0 DocumentationStartStopStep): requires = {'celery.worker.consumer.connection:Connection'} event_dispatcher A app.events.Dispatcher object that can be used to send events. A consumer bootstep must require the Events field for incoming events, which is set to the time of when the event was received. app.events.Dispatcher now accepts a groups argument which decides a white-list of event groups that’ll be sent. The is the group. Currently there are only two groups: worker and task. A dispatcher instantiated as follows: >>> app.events.Dispatcher(connection, groups=['worker']) will only send worker related events0 码力 | 2110 页 | 2.23 MB | 1 年前3
Celery v4.0.0 DocumentationStartStopStep): requires = {'celery.worker.consumer.connection:Connection'} event_dispatcher A app.events.Dispatcher object that can be used to send events. A consumer bootstep must require the Events field for incoming events, which is set to the time of when the event was received. app.events.Dispatcher now accepts a groups argument which decides a white-list of event groups that’ll be sent. The is the group. Currently there are only two groups: worker and task. A dispatcher instantiated as follows: >>> app.events.Dispatcher(connection, groups=['worker']) will only send worker related events0 码力 | 2106 页 | 2.23 MB | 1 年前3
Celery 3.0 DocumentationStartStopStep): requires = {'celery.worker.consumer.connection:Connection'} event_dispatcher A app.events.Dispatcher object that can be used to send events. A consumer bootstep must require the Events 2.11. What’s new in Celery 3.1 (Cipater) 295 Celery Documentation, Release 4.0.0 • app.events.Dispatcher now accepts a groups argument which decides a white-list of event groups that’ll be sent. The is the group. Currently there are only two groups: worker and task. A dispatcher instantiated as follows: >>> app.events.Dispatcher(connection, groups=['worker']) will only send worker related events0 码力 | 703 页 | 2.60 MB | 1 年前3
Celery v4.0.1 DocumentationStartStopStep): requires = {'celery.worker.consumer.connection:Connection'} event_dispatcher A app.events.Dispatcher object that can be used to send events. A consumer bootstep must require the Events field for incoming events, which is set to the time of when the event was received. app.events.Dispatcher now accepts a groups argument which decides a white-list of event groups that’ll be sent. The is the group. Currently there are only two groups: worker and task. A dispatcher instantiated as follows: >>> app.events.Dispatcher(connection, groups=['worker']) will only send worker related events0 码力 | 1040 页 | 1.37 MB | 1 年前3
Celery v4.0.2 DocumentationStartStopStep): requires = {'celery.worker.consumer.connection:Connection'} event_dispatcher A app.events.Dispatcher object that can be used to send events. A consumer bootstep must require the Events field for incoming events, which is set to the time of when the event was received. app.events.Dispatcher now accepts a groups argument which decides a white-list of event groups that’ll be sent. The is the group. Currently there are only two groups: worker and task. A dispatcher instantiated as follows: >>> app.events.Dispatcher(connection, groups=['worker']) will only send worker related events0 码力 | 1042 页 | 1.37 MB | 1 年前3
Celery v4.1.0 DocumentationStartStopStep): requires = {'celery.worker.consumer.connection:Connection'} event_dispatcher A app.events.Dispatcher object that can be used to send events. A consumer bootstep must require the Events 2.11. What’s new in Celery 3.1 (Cipater) 303 Celery Documentation, Release 4.1.0 • app.events.Dispatcher now accepts a groups argument which decides a white-list of event groups that’ll be sent. The is the group. Currently there are only two groups: worker and task. A dispatcher instantiated as follows: >>> app.events.Dispatcher(connection, groups=['worker']) will only send worker related events0 码力 | 714 页 | 2.63 MB | 1 年前3
共 126 条
- 1
- 2
- 3
- 4
- 5
- 6
- 13













