Celery 2.3 DocumentationCostanza", "george@vandelay.com"), ("Cosmo Kramer", "kosmo@vandelay.com"), ) # Email address used as sender (From field). SERVER_EMAIL = "no-reply@vandelay.com" 3.2. Configuration Directives 83 Celery Documentation beat_embedded_init – celery.signals.beat_init Dispatched when celerybeat starts (either standalone or embedded). Sender is the celery.beat.Service instance. 9.15. 2.2.0 151 Celery Documentation, Release 2.3.5 – celery Dispatched in addition to the beat_init signal when celerybeat is started as an embedded process. Sender is the celery.beat.Service instance. • Redis result backend: Removed deprecated settings REDIS_TIMEOUT0 码力 | 334 页 | 1.25 MB | 1 年前3
Celery 2.2 DocumentationCostanza", "george@vandelay.com"), ("Cosmo Kramer", "kosmo@vandelay.com"), ) # E-mail address used as sender (From field). SERVER_EMAIL = "no-reply@vandelay.com" # Mailserver configuration EMAIL_HOST = "mail embedded). Sender is the celery.beat.Service instance. – celery.signals.beat_embedded_init Dispatched in addition to the beat_init signal when celerybeat is started as an embedded process. Sender is the 5672b0e) args=[2, 2] kwargs={} result=4, runtime=0.782663106918 The fields here are, in order: *sender hostname*, *timestamp*, *event type* and *additional event fields*. • AMQP result backend: Now supports0 码力 | 314 页 | 1.26 MB | 1 年前3
Celery 2.2 Documentation"george@vandelay.com"), ("Cosmo Kramer", "kosmo@vandelay.com"), ) # E-mail address used as sender (From field). SERVER_EMAIL = "no-reply@vandelay.com" # Mailserver configuration EMAIL_HOST = "mail embedded). Sender is the celery.beat.Service instance. celery.signals.beat_embedded_init Dispatched in addition to the beat_init signal when celerybeat is started as an embedded process. Sender is the celery b0e) args=[2, 2] kwargs={} result=4, runtime=0.782663106918 The fields here are, in order: *sender hostname*, *timestamp*, *event type* and *additional event fields*. AMQP result backend: Now supports0 码力 | 505 页 | 878.66 KB | 1 年前3
Celery 2.3 DocumentationCostanza", "george@vandelay.com"), ("Cosmo Kramer", "kosmo@vandelay.com"), ) # Email address used as sender (From field). SERVER_EMAIL = "no-reply@vandelay.com" # Mailserver configuration EMAIL_HOST = "mail embedded). Sender is the celery.beat.Service instance. celery.signals.beat_embedded_init Dispatched in addition to the beat_init signal when celerybeat is started as an embedded process. Sender is the celery 2b0e) args=[2, 2] kwargs={} result=4, runtime=0.782663106918 The fields here are, in order: *sender hostname*, *timestamp*, *event type* and *additional event fields*. AMQP result backend: Now supports0 码力 | 530 页 | 900.64 KB | 1 年前3
Celery 2.0 DocumentationCostanza", "george@vandelay.com"), ("Cosmo Kramer", "kosmo@vandelay.com"), ) # E-mail address used as sender (From field). SERVER_EMAIL = "no-reply@vandelay.com" # Mailserver configuration EMAIL_HOST = "mail connecting to the task_sent signal: from celery.signals import task_sent def task_sent_handler(sender=None, task_id=None, task=None, args=None, kwargs=None, **kwds): print("Got signal task_sent for task Documentation, Release 2.0.3 (stable) Some signals also have a sender which you can filter by. For example the task_sent signal uses the task name as a sender, so you can connect your handler to be called only when0 码力 | 165 页 | 492.43 KB | 1 年前3
Celery 3.1 Documentationconnect def task_sent_handler(sender=None, body=None, **kwargs): print('after_task_publish for task id {body[id]}'.format( body=body, )) Some signals also have a sender which you can filter by. For example as a sender, so by providing the sender argument to connect you can connect your handler to be called every time a task with name “proj.tasks.add” is published: @after_task_publish.connect(sender='proj connect(sender='proj.tasks.add') def task_sent_handler(sender=None, body=None, **kwargs): print('after_task_publish for task id {body[id]}'.format( body=body, )) Signals use the same implementation as django.core.dispatch0 码力 | 607 页 | 2.27 MB | 1 年前3
Celery 3.1 Documentationconnect def task_sent_handler(sender=None, body=None, **kwargs): print('after_task_publish for task id {body[id]}'.format( body=body, )) Some signals also have a sender which you can filter by as a sender, so by providing the sender argument to connect you can connect your handler to be called every time a task with name “proj.tasks.add” is published: @after_task_publish.connect(sender='proj connect(sender='proj.tasks.add') def task_sent_handler(sender=None, body=None, **kwargs): print('after_task_publish for task id {body[id]}'.format( body=body, )) Signals use the same implementation as django0 码力 | 887 页 | 1.22 MB | 1 年前3
Celery v5.0.5 Documentationsetup_periodic_tasks(sender, **kwargs): # Calls test('hello') every 10 seconds. sender.add_periodic_task(10.0, test.s('hello'), name='add every 10') # Calls test('world') every 30 seconds sender.add_periodic_task(30 add_periodic_task(30.0, test.s('world'), expires=10) # Executes every Monday morning at 7:30 a.m. sender.add_periodic_task( crontab(hour=7, minute=30, day_of_week=1), test.s('Happy Mondays from celery.signals import after_task_publish @after_task_publish.connect def task_sent_handler(sender=None, headers=None, body=None, **kwargs): # information about task are located in headers for0 码力 | 2315 页 | 2.14 MB | 1 年前3
Celery v5.0.1 Documentationsetup_periodic_tasks(sender, **kwargs): # Calls test('hello') every 10 seconds. sender.add_periodic_task(10.0, test.s('hello'), name='add every 10') # Calls test('world') every 30 seconds sender.add_periodic_task(30 add_periodic_task(30.0, test.s('world'), expires=10) # Executes every Monday morning at 7:30 a.m. sender.add_periodic_task( crontab(hour=7, minute=30, day_of_week=1), test.s('Happy Mondays from celery.signals import after_task_publish @after_task_publish.connect def task_sent_handler(sender=None, headers=None, body=None, **kwargs): # information about task are located in headers for0 码力 | 2313 页 | 2.13 MB | 1 年前3
Celery v5.0.2 Documentationsetup_periodic_tasks(sender, **kwargs): # Calls test('hello') every 10 seconds. sender.add_periodic_task(10.0, test.s('hello'), name='add every 10') # Calls test('world') every 30 seconds sender.add_periodic_task(30 add_periodic_task(30.0, test.s('world'), expires=10) # Executes every Monday morning at 7:30 a.m. sender.add_periodic_task( crontab(hour=7, minute=30, day_of_week=1), test.s('Happy Mondays from celery.signals import after_task_publish @after_task_publish.connect def task_sent_handler(sender=None, headers=None, body=None, **kwargs): # information about task are located in headers for0 码力 | 2313 页 | 2.14 MB | 1 年前3
共 49 条
- 1
- 2
- 3
- 4
- 5













