- update to 0.3.36:
- Updated docs section regarding ``max_years_between_matches`` to be more shorter and hopefully more relevant.
- Add a new initialization parameter ``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.  Fixes #145.
- 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 brief 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 tolerance 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

• Files Changed
• Browse Source

- update to 0.3.34:
  - Feat croniter_range(start, stop, cron)
  - Optimization for poorly written cron expression
  - Make dateutil tz support more official
  - Feat/support for day or

• Files Changed
• Browse Source

- update to 0.3.32:
  - document seconds repeats, fixes #122
  - Implement match method, fixes #54
  - Adding tests for #127 (test more DSTs and croniter behavior around)
  - Changed lag_hours comparison to absolute to manage dst boundary when getting previous

• Files Changed
• Browse Source

- update to 0.3.31:
  - Fix get_next() when start_time less then 1s before next instant

• Files Changed
• Browse Source

• Files Changed
• Browse Source

- Update to 0.3.28:
  * Update credits

• Files Changed
• Browse Source

- Update to 0.3.27:
  * Handle -Sun notation
  * Handle invalid ranges correctly
  * Pypi hygiene
  * fix get_next while perserving the fix of get_prev
  * Don't count previous minute if now is dynamic If the code is triggered from 5-asterisk based cron get_prev based on datetime.now() is expected to return current cron iteration and not previous execution.

• Files Changed
• Browse Source

• Files Changed
• Browse Source

1

• Files Changed
• Browse Source

Automatic submission by obs-autosubmit

• Files Changed
• Browse Source

Automatic submission by obs-autosubmit

• Files Changed
• Browse Source

1

• Files Changed
• Browse Source

Split 13.2 from Factory

• Files Changed
• Browse Source

new OpenStack dep

• Browse Source