Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Relative times containing years fail when computed from a leap day #155
When it is February 29 (like today!),
(It's trying to find February 29 in the following non-leap year, i.e., February 29, 2017.)
I think this is unexpected behavior because people would expect to be able to specify relative time intervals in terms of years on any day. (For example, we had written code that always computes
It must have been an incidental fix; there are no commit messages, comments, or test cases specifically addressing the leap day. A pull request against version 1.5 may be appropriate if anyone affected has time to find and patch the issue.
I have been using parsedatetime master in production on an Alfred workflow since Feb 2015 with no problems (primarily using