I faced issues with django-chronograph's use of date data types. It seemed to have bugs which led to cron jobs being scheduled incorrectly because of time zone issues. It was also not entirely compatible with Python 2.6.
Removing the date compatibility module did not take much away. If the OS, Django and database all use time zones and are set up properly, the rest of the module would work just fine without needing any complicated date transformation layer.
So I created a clone of the Django Chronograph module and removed the date compatibility module.
It is not in the form of a Python installable module yet. But it can be plonked into the application to get it working.
Removing the date compatibility module did not take much away. If the OS, Django and database all use time zones and are set up properly, the rest of the module would work just fine without needing any complicated date transformation layer.
So I created a clone of the Django Chronograph module and removed the date compatibility module.
It is not in the form of a Python installable module yet. But it can be plonked into the application to get it working.
For anyone else who faced similar problems, here's the bitbucket project of my clone: https://bitbucket.org/tanmaykm/tcron
No comments:
Post a Comment