|
1 | 1 | # Changelog |
2 | | -## 1.5.5 (2021-04-26) |
3 | | -* [FIX] [Issue #28](https://github.com/nickmaccarthy/python-datemath/issues/28) |
| 2 | + |
| 3 | +All notable changes to this project will be documented in this file. |
| 4 | + |
| 5 | +The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), |
| 6 | +and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). |
| 7 | + |
| 8 | +## [Unreleased] |
| 9 | +### fixed |
| 10 | +- Fix: Race condition in timezone tests: https://github.com/nickmaccarthy/python-datemath/issues/36 |
| 11 | +- Fix: Updated arrow version: https://github.com/nickmaccarthy/python-datemath/issues/32 |
| 12 | +- Fix: mypy type hint checking in tests: https://github.com/nickmaccarthy/python-datemath/issues/31 |
| 13 | +- Fix: SyntaxWarning: invalid escape sequence in `re.match()`: https://github.com/nickmaccarthy/python-datemath/pull/39 |
| 14 | +- Fix: Licence Classifier: https://github.com/nickmaccarthy/python-datemath/pull/34 |
| 15 | +- Fix: Bump certifi to latest: https://github.com/nickmaccarthy/python-datemath/pull/38 |
| 16 | +### added |
| 17 | +- Feat: Typehint support: https://github.com/nickmaccarthy/python-datemath/issues/31 |
| 18 | +- Feat: Revamed CHANGELOG.md to keepachangelog.org format |
| 19 | + |
| 20 | +### todo |
| 21 | +- todo: Fix pypi: https://github.com/nickmaccarthy/python-datemath/issues/33 |
| 22 | + |
| 23 | +## deprecated |
| 24 | +- python 2.7 support. Python 3.8+ will only be supported going forward |
| 25 | + |
| 26 | +## [1.5.5] - 2021-04-26 |
| 27 | +### fixed |
| 28 | +- fix: [Issue #28](https://github.com/nickmaccarthy/python-datemath/issues/28) |
4 | 29 | * `datemath()` object now returns the expected `datetime` object instead of an `Arrow` object |
5 | 30 | * added tests to catch invalid object types of helpers |
6 | 31 |
|
7 | | -## 1.5.4 (2021-04-20) |
8 | | -* skipped due to name conflict on pypi, all changes in this are from `1.5.3` |
| 32 | +## [1.5.4] - 2021-04-20 |
| 33 | +### Unused |
| 34 | +- skipped due to name conflict on pypi, all changes in this are from `1.5.3` |
9 | 35 |
|
10 | | -## 1.5.3 (2021-04-16) |
11 | | -* [FIX] [Issue #25](https://github.com/nickmaccarthy/python-datemath/issues/25) - Fixed an issue where if you provided an invalid timestamp, i.e. `datemath('2')` you would not get an DateMathException back. Also bumped dependencies. |
| 36 | +## [1.5.3] - 2021-04-16 |
| 37 | +### fixed |
| 38 | +- FIX: [Issue #25](https://github.com/nickmaccarthy/python-datemath/issues/25) - Fixed an issue where if you provided an invalid timestamp, i.e. `datemath('2')` you would not get an DateMathException back. Also bumped dependencies. |
12 | 39 |
|
13 | | -## 1.5.2 (2020-10-01) |
14 | | -* [FIX] [Issue #21](https://github.com/nickmaccarthy/python-datemath/issues/21) - Fixed an issue where if timezone offset was in a datetime string (ISO8601), the timezone of the returned datemath object would be UTC and not the timezone as specified in the datetime string. |
| 40 | +## [1.5.2] - 2020-10-01 |
| 41 | +### fixed |
| 42 | +- FIX: [Issue #21](https://github.com/nickmaccarthy/python-datemath/issues/21) - Fixed an issue where if timezone offset was in a datetime string (ISO8601), the timezone of the returned datemath object would be UTC and not the timezone as specified in the datetime string. |
15 | 43 |
|
16 | 44 | ## 1.5.1 (2020-03-25) |
17 | 45 |
|
18 | | -* [FIX] [Issue #15](https://github.com/nickmaccarthy/python-datemath/issues/15) - Fixed issue with parser finding invalid timeunits and throwing correct errors |
19 | | -* [NEW] [Issue #16](https://github.com/nickmaccarthy/python-datemath/issues/16) - Added support for parser to accecpt a epoch/unix timestamp but throw an error on epoch milli's since arrow can't support that. |
| 46 | +### fixed |
| 47 | +- FIX: [Issue #15](https://github.com/nickmaccarthy/python-datemath/issues/15) - Fixed issue with parser finding invalid timeunits and throwing correct errors |
| 48 | +### added |
| 49 | +- Feat: [Issue #16](https://github.com/nickmaccarthy/python-datemath/issues/16) - Added support for parser to accecpt a epoch/unix timestamp but throw an error on epoch milli's since arrow can't support that. |
20 | 50 |
|
21 | | -## 1.5.0 (2019-11-09) |
| 51 | +## 1.5.0 - 2019-11-09 |
22 | 52 |
|
23 | | -* [FIX] [Issue #12](https://github.com/nickmaccarthy/python-datemath/issues/12) - missing VERSION.txt. Added MANIFEST.in for sdist build |
24 | | -* [FIX] [PR #13](https://github.com/nickmaccarthy/python-datemath/pull/13) - Fix `BaseException` to `Exception` inheritence, thank you for your contribution @yury-primer! |
| 53 | +### fixed |
| 54 | +- [Issue #12](https://github.com/nickmaccarthy/python-datemath/issues/12) - missing VERSION.txt. Added MANIFEST.in for sdist build |
| 55 | +- [PR #13](https://github.com/nickmaccarthy/python-datemath/pull/13) - Fix `BaseException` to `Exception` inheritence, thank you for your contribution @yury-primer! |
25 | 56 |
|
26 | | -## 1.4.9 (2019-10-26) |
| 57 | +## [1.4.9] - 2019-10-26 |
27 | 58 |
|
28 | 59 | ** PLEASE DO NOT USE THIS VERSION, use `1.5.0+` instead. This may not compile on your system due to a missing VERSION.txt which was fixed in `1.5.0+` ** |
29 | | -* [FIX] [Issue #9](https://github.com/nickmaccarthy/python-datemath/issues/9) && [Issue #8](https://github.com/nickmaccarthy/python-datemath/issues/8) - Fixing deprecated arrow `replace()` function with `shift()`. |
30 | | -* [FIX] Arrow upgrade to `0.15.2` to fix the above mentioned issues |
31 | | -* [NEW] Breakout of python2 and python3 requirements |
32 | | -* [NEW] Breakout of python2 and python3 specific CICD pipelines |
33 | | -* [NEW] Derecated the following python version (although they may still work, they are no longer supported) - `2.4`,`2.6`,`3.4`,`3.5` |
34 | | -* [FIX] Modifed `tests.py` to account for the timestamp change (tz is now `+0000`, instead of `-0000`) |
35 | | -* [FIX] replaced `ts = ts.replace(tzinfo=tz.gettz(timezone))` with `ts = ts.replace(tzinfo=timezone)` in `datemath.helpers.parseTime()` to fix [Issue #7](https://github.com/nickmaccarthy/python-datemath/issues/7) |
36 | | - |
37 | | -## v1.4.8 (2019-10-25) |
| 60 | + |
| 61 | +### fixed |
| 62 | +- [FIX] [Issue #9](https://github.com/nickmaccarthy/python-datemath/issues/9) && [Issue #8](https://github.com/nickmaccarthy/python-datemath/issues/8) - Fixing deprecated arrow `replace()` function with `shift()`. |
| 63 | +- [FIX] Arrow upgrade to `0.15.2` to fix the above mentioned issues |
| 64 | +- [FIX] Modifed `tests.py` to account for the timestamp change (tz is now `+0000`, instead of `-0000`) |
| 65 | +- [FIX] replaced `ts = ts.replace(tzinfo=tz.gettz(timezone))` with `ts = ts.replace(tzinfo=timezone)` in `datemath.helpers.parseTime()` to fix [Issue #7](https://github.com/nickmaccarthy/python-datemath/issues/7) |
| 66 | +### added |
| 67 | + |
| 68 | +- [NEW] Breakout of python2 and python3 requirements |
| 69 | +- [NEW] Breakout of python2 and python3 specific CICD pipelines |
| 70 | +- [NEW] Derecated the following python version (although they may still work, they are no longer supported) - `2.4`,`2.6`,`3.4`,`3.5` |
| 71 | + |
| 72 | + |
| 73 | +## [1.4.8] - 2019-10-25 |
| 74 | +** dont use this version ** |
38 | 75 | * skipped due to name conflict on pypi, all changes are in `1.4.9` |
39 | 76 |
|
40 | | -## v1.4.7 (2017-11-10) |
41 | | -* [FIX] Fixed timezone for date strings: [Issue #6](https://github.com/nickmaccarthy/python-datemath/issues/6) |
| 77 | +## [1.4.7] - 2017-11-10 |
| 78 | +### fixed |
| 79 | +- [FIX] Fixed timezone for date strings: [Issue #6](https://github.com/nickmaccarthy/python-datemath/issues/6) |
42 | 80 |
|
43 | | -## v1.4.5 (2017-03-21) |
44 | | -* [NEW] Added roundDown functionality. Allows user to specify the default rounding for expressions such as `/d`. |
45 | | -* example - assuming the time is currently 2016-01-01 12:00:00, we should get the following |
| 81 | +## [1.4.5] - 2017-03-21 |
| 82 | +### added |
| 83 | +- [NEW] Added roundDown functionality. Allows user to specify the default rounding for expressions such as `/d`. |
| 84 | +- example - assuming the time is currently 2016-01-01 12:00:00, we should get the following |
46 | 85 | ``` |
47 | 86 | >>> # now = 2016-01-01 14:00:00+00:00 |
48 | 87 | >>> dm('now+/d', roundDown=False) |
|
51 | 90 | <Arrow [2016-01-01T00:00:00+00:00]> |
52 | 91 | ``` |
53 | 92 |
|
54 | | -## v1.4.4 (2016-12-28) |
55 | | -* [FIX] Fixed bug with expression logic and rounding: https://github.com/nickmaccarthy/python-datemath/pull/2 |
| 93 | +## [1.4.4] - 2016-12-28 |
| 94 | +### fixed |
| 95 | +- [FIX] Fixed bug with expression logic and rounding: https://github.com/nickmaccarthy/python-datemath/pull/2 |
56 | 96 |
|
57 | | -## 1.4.3 (2016-03-31) |
58 | | -* [NEW] Floats are now supported for days, hours, and seconds units. Example ```now-2.5d```, ```now-3.2h```. Any other unit other than days, hours, or seconds that is a float will be converted to an int and floored due to the datetime() module not being able to handle them. |
| 97 | +## [1.4.3] - 2016-03-31 |
| 98 | +### added |
| 99 | +[NEW] Floats are now supported for days, hours, and seconds units. Example ```now-2.5d```, ```now-3.2h```. Any other unit other than days, hours, or seconds that is a float will be converted to an int and floored due to the datetime() module not being able to handle them. |
0 commit comments