Why is timezone referred to as a field in the docs but its not released?

[viperfx]

The current release is 1.1.1, but when you install it, or you take a look at the tag on github, the migration does not involve the timezone field for the 0006 migration file.

What is going on with this?

[viiicky]

yeah, The README is updated as the code is merged to master, but the feature is not released yet. These are the commits made since last release i.e. since v.1.1.1: v1.1.1...master

@ask @DDevine @thedrow @ShaheedHaque @auvipy @mbaechtold @wardal @mheppner any idea on the next release date?

I am evaluating django-celery-beat for my scheduling needs and two of the most needed important features shall become live on the next release:

• Allow timezone-aware Cron schedules (Allow timezone-aware Cron schedules #99) 397c2c6 cc @tartieret
• Support Periodic Tasks with a start date and one-off tasks (Support Periodic Tasks with a start date and one-off tasks  #78) 27f73a5 cc @oubeichen

Many Thanks

[thedrow]

I'll work on a release as soon as I can.

[viiicky]

ok, thanks @thedrow

[devangmehta123]

Is it safe to use the master branch in our requirements before the next release? We really need the timezone setting feature for the tasks.

We are struggling to get CELERY_TIMEZONE to be recognized as 'Europe/London'. It always works as UTC.

Our Django is 1.10.2, celery is 4.2.1, django-celery-beat is 1.1.1

I have filed a separate issue for this: #161

[auvipy]

you can use it

[thedrow]

I'm really sorry for the delay.
I've been extremely busy.
Can you please check if 1.2.0 resolves your issue?

[auvipy]

Omer, could you also push django-celery-result to pypi?

[thedrow]

I'll try to get to it in the next few days.

[viperfx]

any updates? ive been using a crude solution for scheduling which is check to fire tasks every minute. But its better than dealing with all the bugs right now

[viperfx]

@viiicky what have you done to solve your scheduling needs since your original comment?

[viiicky]

@viperfx after testing django-celery-beat quite a lot, I made the decision to not use Celery for our scheduling needs.

We are still using Celery, but just for workers. For scheduling purposes, we have put an APScheduler in front.

APScehduler turned out to be much more mature and reliable for scheduling purposes.

In fact our stuff is already live in production now.

We make our scheduler put the messages in queue at desired times and let workers eat those messages immediately.

[viperfx]

@viiicky thanks for the reply.

Are you using APScheduler with a database backend? E.g. is there tables that maintain a schedule for tasks should fire? does it handle timezones as well?

[viiicky]

@viperfx yes we are using database storage for APScehduler.

It maintains a running records of jobs in a table. And the row is present in the DB unless the schedule ends. If the job repeats indefinitely, the row doesn't get deleted ever for that job.

Yes, it has support for Timezones as well. For simplicity, we are using UTC for everything. But nothing stops us from using timezones.

[viperfx]

@viiicky okay thanks. That sounds promising.

It sounds like you are scheduling the job programmatically. I am looking to have the schedule or Cron set in a database.

Do you have an example of how Django models can be setup to use APScheduler?

[auvipy]

this should be fixed now