However, I spent a lot of time debugging an issue because I assumed that a length 6 entry () would be interpreted minute-hour-date-month-day-year. Instead, seems to be interpreted as second-minute-hour-date-month-day. The wikipedia entry for cron shows the former, thus my confusion:
I think this is a big problem not only because of the confusion it might cause to people googling for the cron spec (like myself), but also because it causes very inconsistent behavior of get_next().
See below.
If you specify a length 5 cron entry, get_next returns datetimes every minute:
But if you specify a length 6 cron entry, suddenly it switches to every second.
If you want to keep this behavior, it would be great for it to be documented better -- and perhaps for croniter to issue a warning when the user attempts a length 6 entry.
Great package! Really handy.
However, I spent a lot of time debugging an issue because I assumed that a length 6 entry ( ) would be interpreted minute-hour-date-month-day-year. Instead, seems to be interpreted as second-minute-hour-date-month-day. The wikipedia entry for cron shows the former, thus my confusion:
I think this is a big problem not only because of the confusion it might cause to people googling for the cron spec (like myself), but also because it causes very inconsistent behavior of
get_next()
. See below.If you specify a length 5 cron entry, get_next returns datetimes every minute:
But if you specify a length 6 cron entry, suddenly it switches to every second.
If you want to keep this behavior, it would be great for it to be documented better -- and perhaps for croniter to issue a warning when the user attempts a length 6 entry.