python-croniter/python-croniter.changes

-------------------------------------------------------------------
Thu Nov 26 09:22:47 UTC 2020 - Dirk Mueller <dmueller@suse.com>

- 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

-------------------------------------------------------------------
Fri Jul 17 07:25:05 UTC 2020 - Dirk Mueller <dmueller@suse.com>

- 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

-------------------------------------------------------------------
Mon Jun  8 13:31:08 UTC 2020 - Dirk Mueller <dmueller@suse.com>

- 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

-------------------------------------------------------------------
Sat Mar 14 15:47:06 UTC 2020 - Dirk Mueller <dmueller@suse.com>

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

-------------------------------------------------------------------
Thu May 23 06:36:54 UTC 2019 - pgajdos@suse.com

- version update to 0.3.30
  * credits
  * history stripping (security)
  * Handle -Sun notation
  * Handle invalid ranges correctly

-------------------------------------------------------------------
Tue Mar 26 13:35:14 UTC 2019 - Tomáš Chvátal <tchvatal@suse.com>

- Update to 0.3.28:
  * Update credits

-------------------------------------------------------------------
Thu Mar  7 13:48:40 UTC 2019 - Tomáš Chvátal <tchvatal@suse.com>

- 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.

-------------------------------------------------------------------
Wed Oct 17 18:29:01 UTC 2018 - Jan Engelhardt <jengelh@inai.de>

- Avoid name repetition in summary.

-------------------------------------------------------------------
Wed Oct 17 13:29:54 UTC 2018 - sjamgade@suse.com

- update to 0.3.20
  - (tag: 0.3.20) Preparing release 0.3.20
  -  pep8
  -  Fix sao paulo timezone test.
  -  remove outdated comment
  -  correctly handle DST changes
  -  Merge pull request #89 from kiorky/master
  -  Back to development: 0.3.20
  -  (tag: 0.3.19) Preparing release 0.3.19
  -  fix #87: backward dst changes
  -  Merge pull request #88 from kiorky/master
  -  Back to development: 0.3.19
  -  (tag: 0.3.18) Preparing release 0.3.18
  -  Merge pull request #18 from taichino/master
  -  Merge pull request #86 from otherpirate/master
  -  Adding is_valid class method to readme
  -  Adding class method is_valid to validate cron syntax
  -  Creating base croniter error
  -  Merge pull request #85 from kiorky/master
  -  Back to development: 0.3.18
 

-------------------------------------------------------------------
Fri Aug 25 07:05:44 UTC 2017 - tbechtold@suse.com

- update to 0.3.17:
  - DOW occurence sharp style support.
  - Better test suite
  - DST support
  - fix bug around multiple conditions and range_val in
    _get_prev_nearest_diff.
  - issue #69: added day_or option to change behavior when day-of-month and
    day-of-week is given
  - `Real fix for #34
  - `Modernize test infra
  - `Release as a universal wheel
  - `Raise ValueError on negative numbers
  - `Compare types using "issubclass" instead of exact match
  - `Implement step cron with a variable base
- convert to singlespec

-------------------------------------------------------------------
Tue Nov 15 10:24:09 UTC 2016 - dmueller@suse.com

- update to 0.3.12

-------------------------------------------------------------------
Wed Apr 13 08:15:37 UTC 2016 - dmueller@suse.com

- switch to python-python-dateutil

-------------------------------------------------------------------
Mon Sep 15 08:45:58 UTC 2014 - tbechtold@suse.com

- update to version 0.3.5:
  * support for 'l' (last day of month)

-------------------------------------------------------------------
Fri Mar  7 12:55:49 UTC 2014 - speilicke@suse.com

- Package docs/LICENSE

-------------------------------------------------------------------
Fri Mar  7 10:01:08 UTC 2014 - speilicke@suse.com

- Fix requirement on python-dateutil (not python-python-dateutil as upstream)

-------------------------------------------------------------------
Fri Mar  7 08:31:20 UTC 2014 - speilicke@suse.com

- Initial version