CELERY_TIMEZONE = "Europe/London" Django Users For Django users the timezone specified in the TIME_ZONE setting will be used, but not if the :set- ting:‘CELERY_ENABLE_UTC‘ setting is enabled. Celery by default in version 3.0. Note: django-celery will use the local timezone as specified by the TIME_ZONE setting, it will also honor the new USE_TZ setting introuced in Django 1.4. 10.4.2 New security

CELERY_TIMEZONE = "Europe/London" Django Users For Django users the timezone specified in the TIME_ZONE setting will be used, but not if the :setting:`CELERY_ENABLE_UTC` setting is enabled. Celery is by default in version 3.0. Note django-celery will use the local timezone as specified by the TIME_ZONE setting, it will also honor the new USE_TZ [https://docs.djangoproject.com/en/dev/topics/i18n/timezones/]

the new USE_TZ setting introduced in Django 1.4. For Django users the time zone specified in the TIME_ZONE setting will be used, or you can specify a custom time zone for Celery alone by using the CELERY_TIMEZONE by default in version 3.0. Note: django-celery will use the local timezone as specified by the TIME_ZONE setting, it will also honor the new USE_TZ setting introuced in Django 1.4. New security serializer

the new USE_TZ setting introduced in Django 1.4. For Django users the time zone specified in the TIME_ZONE setting will be used, or you can specify a custom time zone for Celery alone by using the CELERY_TIMEZONE by default in version 3.0. Note django-celery will use the local timezone as specified by the TIME_ZONE setting, it will also honor the new USE_TZ [https://docs.djangoproject.com/en/dev/topics/i18n/timezones/]

the new USE_TZ setting introduced in Django 1.4. For Django users the time zone specified in the TIME_ZONE setting will be used, or you can specify a custom time zone for Celery alone by using the timezone Documentation, Release 4.0.0 Note: django-celery will use the local timezone as specified by the TIME_ZONE setting, it will also honor the new USE_TZ setting introduced in Django 1.4. New security serializer

the new USE_TZ setting introduced in Django 1.4. For Django users the time zone specified in the TIME_ZONE setting will be used, or you can specify a custom time zone for Celery alone by using the timezone django-celery [https://pypi.python.org/pypi/django-celery/] will use the local timezone as specified by the TIME_ZONE setting, it will also honor the new USE_TZ [https://docs.djangoproject.com/en/dev/topics/i18n/timezones/]

the new USE_TZ setting introduced in Django 1.4. For Django users the time zone specified in the TIME_ZONE setting will be used, or you can specify a custom time zone for Celery alone by using the timezone django-celery [https://pypi.python.org/pypi/django-celery/] will use the local timezone as specified by the TIME_ZONE setting, it will also honor the new USE_TZ [https://docs.djangoproject.com/en/dev/topics/i18n/timezones/]

the new USE_TZ setting introduced in Django 1.4. For Django users the time zone specified in the TIME_ZONE setting will be used, or you can specify a custom time zone for Celery alone by using the timezone Documentation, Release 4.1.0 Note: django-celery will use the local timezone as specified by the TIME_ZONE setting, it will also honor the new USE_TZ setting introduced in Django 1.4. New security serializer

the new USE_TZ setting introduced in Django 1.4. For Django users the time zone specified in the TIME_ZONE setting will be used, or you can specify a custom time zone for Celery alone by using the timezone by default in version 3.0. Note: django-celery will use the local timezone as specified by the TIME_ZONE setting, it will also honor the new USE_TZ setting introduced in Django 1.4. New security serializer

the new USE_TZ setting introduced in Django 1.4. For Django users the time zone specified in the TIME_ZONE setting will be used, or you can specify a custom time zone for Celery alone by using the timezone django-celery [https://pypi.python.org/pypi/django-celery/] will use the local timezone as specified by the TIME_ZONE setting, it will also honor the new USE_TZ [https://docs.djangoproject.com/en/dev/topics/i18n/timezones/]