|
Upgrade to release 0.3.35:
- Handle L in ranges.
- Add a new initializaton paramter max_years_between_matches to
support finding the next/previous date beyond the default 1 year
window, if so desired. Updated README to include additional
notes and example of this usage.
- The croniter_range() function was updated to automatically
determines the appropriate max_years_between_matches value, this
preventing handling of the CroniterBadDateError exception.
- Updated exception handling classes: CroniterBadDateError now
only applies during date finding operations (next/prev), and all
parsing errors can now be caught using CroniterBadCronError. The
CroniterNotAlphaError exception is now a subclass of
CroniterBadCronError. A breif description of each exception
class was added as an inline docstring.
- Updated iterable interfaces to replace the CroniterBadDateError
with StopIteration if (and only if) the max_years_between_matches
argument is provided. The rationale here is that if the user has
specified the max tollernace between matches, then there's no need
to further inform them of no additional matches. Just stop the
iteration. This also keeps backwards compatibility.
- Minor docs update.
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Acked-by: Trevor Gamblin <trevor.gamblin@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
Leon Anavi