- update to 2.0.5:
  * No changes, fix lint
  * Support hashid strings in is_valid
  * Avoid over-optimization in crontab expansions

• Files Changed
• Browse Source

- update to 2.0.3:
  * Add match_range function [salitaba]

• Files Changed
• Browse Source

- update to 2.0.2:
  * fix leap year (29 days in February) [zed2015]

• Files Changed
• Browse Source

- update to 2.0.1:
  * Fix release issue
  * Add Python 3.12 support
  * Make major release instructions

  * Add a way to make next() easier to use. This fixes #11 [kiorky]
    now raises a CroniterBadDateError.

• Files Changed
• Browse Source

- Update to 1.4.1:
  * Make a retrocompatible version of 1.4.0 change about supporting
    VIXIECRON bug.
  * Added "implement_cron_bug" flag to make the cron parser compatible
    with a bug in Vixie/ISC Cron.
- Switch to pyproject macros.
- Actually drop future requirement.
- Stop using greedy globs in %files.

• Files Changed
• Browse Source

• Files Changed
• Browse Source

- update to 1.3.15:
  * Fix hashed expressions omitting some entries
  * Enhance .match() precision for 6 position expressions

• Files Changed
• Browse Source

- update to 1.3.14:
  * Add check for range begin/end
  * restore py2 compat
  *  Do not expose `i` into global namespace
  * Fix DOW hash parsing [kiorky]
  * better error handling on py3 [kiorky]
  * Add Python 3.11 support and move docs files to main folder

• Files Changed
• Browse Source

- use https for urls

• Files Changed
• Browse Source

• Files Changed
• Browse Source

- update to 1.2.0:
  * Enforce validation for day=1. Before this release we used to support day=0
    and it was silently glided to day=1 to support having both day in day in
    4th field when it came to have 6fields cron forms (second repeat). It will
    now raises a CroniterBadDateError.

• Files Changed
• Browse Source

- update to 1.1.0:
  * Enforce validation for month=1. Before this release we used to support
    month=0 and it was silently glided to month=1 to support having both day in
    month in 4th field when it came to have 6fields cron forms

• Files Changed
• Browse Source

- update to 1.0.15:
  * restore py2
  * better type checks

• Files Changed
• Browse Source

- update to 1.0.13:
  * Fix ZeroDivisionError with ``* * R/0 * *``
  * Add support for hashed/random/keyword expressions
  * Review support support for hashed/random/keyword expression and add expanders reactor
  * fix bug: bad case:``0 6 30 3 *``
  * Create ``CroniterUnsupportedSyntaxError`` exception for situations where CRON syntax may be valid but some combinations of features is not supported.
    This *may* impact existing cron expressions in prior releases, because ``0 0 * * 15,sat#1`` was previously allowed but incorrectly handled.
  * Update ``croniter_range()`` to allow an alternate ``croniter`` class to be used.  Helpful when using a custom class derived from croniter.
  * Remove external library ``natsort``.

• Files Changed
• Browse Source

• Files Changed
• Browse Source

- Update to 1.0.8:
  * Update `_expand` to lowercase each component of the expression.
  * Fix _expand to reject int literals with underscores
  * Fix combination of star and invalid expression bugs
  * Security fix: fix overflow when using cron ranges
  * Fix #155: raise CroniterBadCronError when error syntax
  * Fix match when datetime has microseconds
  * Added Python 3.8 and 3.9 support

• Files Changed
• Browse Source

- 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