Scheduling morning emails with Python and Celery
cucumbertown.com
Scheduling morning emails with Python and Celery
1–10 of 19 posts
Re: Scheduling morning emails with Python and Celery
#2[deleted]
Re: Scheduling morning emails with Python and Celery
#3alternatively: use uWSGI cron
http://uwsgi-docs.readthedocs.org/en/latest/PythonDecorators...
Re: Scheduling morning emails with Python and Celery
#4This doesn't handle daylight saving time.
Re: Scheduling morning emails with Python and Celery
#5Would this create a problem around Daylight Saving Time until the user logs in again to reset their time offset?
Re: Scheduling morning emails with Python and Celery
#6This doesn't handle daylight saving time.
It does take care of DST: http://www.w3schools.com/jsref/jsref_gettimezoneoffset.asp
Re: Scheduling morning emails with Python and Celery
#7Would this create a problem around Daylight Saving Time until the user logs in again to reset their time offset?
getTimezoneOffset() would return the value after taking care of DST. So there shouldn't be any DST related inconsistencies. Now if the user moves to another timezone, and never hits one of our page, there is no direct way of tracking his/her change in location.
Re: Scheduling morning emails with Python and Celery
#8Would this create a problem around Daylight Saving Time until the user logs in again to reset their time offset?
getTimezoneOffset() would return the value after taking care of DST. So there shouldn't be any DST related inconsistencies. Now if the user moves to another timezone, and never hits one of our page, there is no direct way of tracking his/her change in location.
I mean that starting mid-March a user who had previously been in a -8:00 UTC offset would then be in a -7:00 UTC offset and you wouldn't know the timezone offset changed until they visited the website again.
Re: Scheduling morning emails with Python and Celery
#9alternatively: use uWSGI cron http://uwsgi-docs.readthedocs.org/en/latest/PythonDecorators...
Good one! People relying on Cron could benefit from this.
Re: Scheduling morning emails with Python and Celery
#10Earlier quoted context omitted.
getTimezoneOffset() would return the value after taking care of DST. So there shouldn't be any DST related inconsistencies. Now if the user moves to another timezone, and never hits one of our page, there is no direct way of tracking his/her change in location.
I mean that starting mid-March a user who had previously been in a -8:00 UTC offset would then be in a -7:00 UTC offset and you wouldn't know the timezone offset changed until they visited the website again.
That’s certainly a problem. But this solution is better than being totally off. Worst case the person gets the mail in the previous timezone he registered which should be before the DST.