summaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* feat: Support for day-or in matchdevs田口信元2020-06-082-2/+32
|
* Fix sorting on py3Mathieu Le Marec - Pasquet2020-05-271-1/+2
| | | | This fixes #127
* Fix styleMathieu Le Marec - Pasquet2020-05-271-11/+12
|
* Add more DST testsMathieu Le Marec - Pasquet2020-05-271-1/+55
|
* Test for #127Mathieu Le Marec - Pasquet2020-05-271-0/+5
| | | | This fixes #127
* Add datetime/crontab match method.Mathieu Le Marec - Pasquet2020-05-272-0/+23
| | | | Implement and fixes #54.
* Document more second repeats.Mathieu Le Marec - Pasquet2020-05-272-8/+29
| | | | This fixes taichino/croniter#122
* Changed lag_hours comparison to absolute to manage dst boundary when getting ↵Sokkka2020-05-182-2/+23
| | | | previous
* Fix get_next() when start_time less then 1s before next instantAlex Hill2020-01-022-19/+38
|
* Handle -Sun notationMathieu Le Marec - Pasquet2019-03-262-3/+73
| | | | This fixes #119.
* Handle invalid ranges correctlyMathieu Le Marec - Pasquet2019-03-262-1/+8
| | | | This fixes #114
* (fix#107): microsecond thresholdMathieu Le Marec - Pasquet2018-06-202-0/+23
|
* fix `get_next` while perserving the fix of `get_prev` in 7661c2aaaAvikam Agur2018-05-222-1/+18
|
* Don't count previous minute if now is dynamicIgor Khrol2018-03-052-1/+8
| | | | 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.
* Fix sao paulo timezone test.Kevin Rose2017-11-061-4/+4
|
* remove outdated commentKevin Rose2017-11-061-1/+0
|
* correctly handle DST changesKevin Rose2017-11-061-11/+6
|
* fix #87: backward dst changesMathieu Le Marec - Pasquet2017-08-312-15/+69
|
* pep8Mathieu Le Marec - Pasquet2017-08-311-3/+6
|
* Adding class method is_valid to validate cron syntaxotherpirate2017-07-062-99/+127
|
* Creating base croniter errorotherpirate2017-07-061-6/+10
|
* Address issue #68Kengo Seki2017-05-212-15/+126
|
* Flake8 Compliance and TestMathieu Le Marec - Pasquet2017-03-151-10/+14
|\
| * Finding and fixing flake8 violations; adding flake8 as a test depMichael Crilly2017-03-101-10/+14
| |
* | Implement DST supportMathieu Le Marec - Pasquet2017-03-152-4/+66
|/ | | | This fixes https://github.com/taichino/croniter/issues/82
* fix bug around multiple conditions and range_val inYuki Chiba2017-02-162-1/+74
| | | | _get_prev_nearest_diff
* issue #69: added day_or option to change behavior when day-of-month and ↵Andreas Vogl2016-12-222-2/+21
| | | | | | | | day-of-week is given cron defineds that day-of-month and day-of-week should be connected using OR, however, an AND connection would be expected by some users as it is implemented in fcron. This day_or option allows to switch between the behaviour
* py3 fixMathieu Le Marec - Pasquet2012-04-131-3/+4
|
* py 26 fixMathieu Le Marec - Pasquet2012-04-121-1/+2
|
* Real fix for #3434Mathieu Le Marec - Pasquet2016-10-303-19/+30
|
* Merge pull request #60 from josegonzalez/issue-57Mathieu Le Marec - Pasquet2016-11-012-2/+37
|\ | | | | Implement step cron with a variable base
| * Implement step cron with a variable baseJose Diaz-Gonzalez2016-08-152-2/+37
| | | | | | | | Closes #57
* | Merge pull request #63 from josegonzalez/issue-25Mathieu Le Marec - Pasquet2016-11-011-0/+4
|\ \ | | | | | | Raise ValueError on negative numbers
| * | Update error messageJose Diaz-Gonzalez2016-10-271-1/+1
| | |
| * | Raise ValueError on negative numbersJose Diaz-Gonzalez2016-08-151-0/+4
| |/ | | | | | | Closes #25
* | Compare types using `issubclass` instead of exact matchLeonid Evdokimov2016-10-131-3/+3
|/ | | | | | | | | | It makes life with mocked datetime a bit easier as one can mock imported datetime and create a class derived from datetime.datetime, but can't mock datetime itself as it's C library. Examples of alike FakeDatetime may be found here: - https://github.com/apache/incubator-airflow/blob/master/tests/ti_deps/deps/runnable_exec_date_dep.py - https://github.com/TheTorProject/ooni-probe/blob/master/ooni/tests/test_scheduler.py
* Merge pull request #65 from int3rlop3r/masterMathieu Le Marec - Pasquet2016-08-152-4/+13
|\ | | | | Better handling of invalid expressions
| * Better handling of invalid expressionsJonathan2016-08-072-4/+13
| | | | | | | | | | | | | | Expressions such as negative values and invalid characters used to throw a KeyError with a not so helpful error message. In this change invalid expressions will throw a ValueError with a more helpful error message.
* | Changed shebangJonathan Fernandes2016-08-071-1/+1
|/ | | Changed shebang to use the right python version.
* Add testcase to prove that issue 34 is still not parseableJose Diaz-Gonzalez2016-07-271-0/+5
|
* Fix error message when not able to find a previous dateJose Diaz-Gonzalez2016-07-271-1/+3
| | | | Refs #34
* support setting ret_type in __init__Brent Tubbs2016-02-241-11/+15
|
* Bug fix: The get_prev API crashed when last day of month token was used. ↵iddo2016-01-122-1/+48
| | | | Some essential logic was missing.
* The fuctionality of 'l' as day of month was brokne, since the month variable ↵iddoav/bug/last_day_of_month_is_not_correctiddo2015-11-232-0/+17
| | | | was not properly updated
* added python 2.6 comment so it won't be deletedPeter van 't Zand2015-11-191-2/+3
|
* the function should be a class method instead of instance method because it ↵Peter van 't Zand2015-07-151-1/+2
| | | | doesn't perform an action on the instance
* created timedelta to seconds function because python2.6-datetime doesn't ↵Peter van 't Zand2015-07-152-2/+11
| | | | support .total_seconds()
* Truncate microseconds by setting to 0Corey Wright2015-06-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | To maintain backwards compatible behavior and comparability of time values returned by croniter, truncate microseconds from return value of get_(prev|next) by setting it to 0. Commit f7e14967 replaced `mktime(dst.timetuple())`, which truncates microseconds as timetuple() omits microseconds, with `self._datetime_to_timestamp(dst)` which maintains microseconds. This commit sets microseconds to 0, effectively truncating microseconds as was done previously. Always setting microseconds to 0 is inline with the maintained behavior of settings seconds to 0 when the cron format omits seconds (ie 5 column cron format) as the cron format always omits microseconds. Currently time values returned by croniter are not easily compared when the start time differs, if only in microseconds, because the start time's microseconds are maintained in the output of get_(prev|next). The start time commonly differs when the time value is communicated between application executions (eg in a database) or between different applications (eg over the network). So restoring the previous behavior not only restores backwards compatibility, but also restores the ability to compare croniter time values.
* Fixed #40Steffen Schröder2015-05-302-2/+13
| | | | | Issue: converting sun in range sun-thu transforms to int 0 which is recognized as empty string Solution converting sun to string "0"
* Merge remote-tracking branch 'origin/master'Mathieu Le Marec - Pasquet2015-05-291-2/+5
|\
View Lorry Controller Status