Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update croniter to 5.0.1 #3121

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update croniter to 5.0.1 #3121

wants to merge 1 commit into from

Conversation

pyup-bot
Copy link
Collaborator

This PR updates croniter from 0.3.34 to 5.0.1.

Changelog

5.0.1

------------------

- Community wanted: Reintroduce 7 as DayOfWeek in deviation from standard cron (90). [kiorky]

4.0.0

------------------

- Remove DayOfWeek alias 7 to DayOfWeek 0 to stick to standard cron (90). [kiorky]
- Fix DOW ranges calculations when lastday is a Sunday. [kiorky]

3.0.4

------------------

- Fix overflow on 32bits systems (87) [kiorky]
- Fix python2 testing (related to 93) [kiorky]
- Modernize packaging. Special thanks to Aarni Koskela (akx) for all the inputs. [kiorky, akx]

3.0.3

------------------

- fix lint [kiorky]

3.0.2

------------------

- Fix start_time not respected in get_next/get_prev/all_next/all_prev (86) [hesstobi, kiorky]

3.0.1

------------------

- Add an `update_current` argument to get_next/get_prev/all_next/all_prev to facilitate writing of some downstream code, see 83. [kiorky]

3.0.0

------------------

- Support for year field [zhouyizhen, kiorky]
- Better support for 6 fields (second), and 7 fields crons [zhouyizhen, kiorky]
- Better fix hashed expressions omitting some entries (82, 42, 30) fix is retained over 42 initial fix [zhouyizhen, kiorky]
- Ensure match return false when not time available (81) [zhouyizhen, kiorky]

2.0.7

------------------

- fix doc

2.0.6

------------------

- Implement second_at_beginning [zhouyizhen, kiorky]
- Support question mark as wildcard [zhouyizhen, kiorky]
- Support to start a cron from a reference start time [mghextreme, kiorky]

2.0.5

------------------

- No changes, fix lint [kiorky]

2.0.4

------------------

- Support hashid strings in is_valid [george-kuanli-peng, kiorky]
- Avoid over-optimization in crontab expansions [Cherie0125, liqirui <liqiruibaidu.com>, kiorky]

2.0.3

------------------

- Add match_range function [salitaba]

2.0.2

------------------

- fix leap year (29 days in February) [zed2015]

2.0.1

------------------

- Fix release issue [kiorky]

2.0.0

------------------

- Add Python 3.12 support [rafsaf]
- Make major release instructions [kiorky]

1.4.1

------------------

- Make a retrocompatible version of 1.4.0 change about supporting VIXIECRON bug. (fix 47)
[kiorky]

1.4.0

------------------

- Added "implement_cron_bug" flag to make the cron parser compatible with a bug in Vixie/ISC Cron
[kiorky, David White <dwhite2cisco.com>]
*WARNING*: EXPAND METHOD CHANGES RETURN VALUE

1.3.15

-------------------

- Fix hashed expressions omitting some entries
[waltervos/Walter Vos <walter.vosns.nl>]
- Enhance .match() precision for 6 position expressions
[szpol/szymon <szymon.polinkiewiczgmail.com>]

1.3.14

-------------------

- Lint

1.3.13

-------------------

- Add check for range begin/end

1.3.12

-------------------

- restore py2 compat

1.3.11

-------------------

-  Do not expose `i` into global namespace

1.3.10

-------------------

- Fix DOW hash parsing [kiorky]
- better error handling on py3 [kiorky]

1.3.8

------------------

- Add Python 3.11 support and move docs files to main folder [rafsaf]

1.3.7

------------------

- fix tests
- Fix croniter_range infinite loop  [Shachar Snapiri <ssnapiripaloaltonetworks.com>]

1.3.5

------------------

- Add Python 3.10 support [eelkevdbos]

1.3.4

------------------

- Really fix compat for tests under py27
[kiorky]

1.3.3

------------------

- Fix compat for tests under py27
[kiorky]

1.3.2

------------------

- Fix 12: regressions with set_current
[kiorky, agateblue]

1.3.1

------------------

- Restore compat with python2
[kiorky]

1.3.0

------------------

- Add a way to make next() easier to use. This fixes 11
[kiorky]

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. See https://github.com/kiorky/croniter/issues/6
[kiorky]

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 (second repeat). It will now raises a CroniterBadDateError. See https://github.com/kiorky/croniter/issues/6
[kiorky]

1.0.15

-------------------

- restore py2 [kiorky]

1.0.14

-------------------

- better type checks [kiorky]

1.0.13

-------------------

- Fix ZeroDivisionError with ``* * R/0 * *``
[cuu508]

1.0.12

-------------------

- Add support for hashed/random/keyword expressions
Ryan Finnie (rfinnie)
- Review support support for hashed/random/keyword expression and add expanders reactor
[ kiorky ]

1.0.11

-------------------

- fix bug: bad case:``0 6 30 3 *``
[zed2015(zhangchi)]
- Add support for ``L`` in the day_of_week component.  This enable expressions like ``* * * * L4``, which means last Thursday of the month.  This resolves 159.
[Kintyre]
- Create ``CroniterUnsupportedSyntaxError`` exception for situations where CRON syntax may be valid but some combinations of features is not supported.
Currently, this is used when the ``day_of_week`` component has a combination of literal values and nth/last syntax at the same time.
For example, ``0 0 * * 1,L6`` or ``0 0 * * 15,sat1`` will both raise this exception because of mixing literal days of the week with nth-weekday or last-weekday syntax.
This *may* impact existing cron expressions in prior releases, because ``0 0 * * 15,sat1`` was previously allowed but incorrectly handled.
[Kintyre]

- Update ``croniter_range()`` to allow an alternate ``croniter`` class to be used.  Helpful when using a custom class derived from croniter.
[Kintyre]

1.0.10

-------------------

- Remove external library ``natsort``.
Sorting of cron expression components now handled with ``sorted()`` with a custom ``key`` function.
[Kintyre]

1.0.9

------------------

- Remove futures dependency
[kiorky]

1.0.8

------------------

- Update `_expand` to lowercase each component of the expression.
This is in relation to 157. With this change, croniter accepts and correctly handles `* * 10-L * *`.
[cuu508]

1.0.7

------------------

- Fix _expand to reject int literals with underscores
[cuu508]
- Remove a debug statement to make flake8 happy
[cuu508]

1.0.6

------------------

- Fix combination of star and invalid expression bugs
[kiorky]

1.0.5

------------------

- Security fix: fix overflow when using cron ranges
[kiorky]

1.0.4

------------------

- Spelling fix release

1.0.3

------------------

- Fix 155: raise CroniterBadCronError when error syntax
[kiorky]

1.0.2

------------------

- Fix match when datetime has microseconds
[kiorky]

1.0.1

------------------
- no changes, just to make sense with new semver2 (making croniter on a stable state)
[kiorky]

0.3.37

-------------------

- Added Python 3.8 and 3.9 support
[eumiro]

0.3.36

-------------------

- Updated docs section regarding ``max_years_between_matches`` to be more shorter and hopefully more relevant.
[Kintyre]
- Don't install tests
[scop]

0.3.35

-------------------

- Handle L in ranges. This fixes 142.
[kiorky]
- 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.
[Kintyre]
- The ``croniter_range()`` function was updated to automatically determines the appropriate ``max_years_between_matches`` value, this preventing handling of the ``CroniterBadDateError`` exception.
[Kintyre]
- 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.
[Kintyre]
- 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.
[Kintyre]
- Minor docs update
[Kintyre]
Links

@pyup-bot pyup-bot mentioned this pull request Oct 29, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@pyup-bot