Skip to content

Conversation

@jswhit
Copy link
Collaborator

@jswhit jswhit commented Jul 17, 2020

closes #187 and #189

Jeff Whitaker added 2 commits July 16, 2020 20:54
Copy link
Collaborator

@spencerkclark spencerkclark left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @jswhit -- I think this makes sense. It does prevent exact roundtripping with non-microsecond units in the case when dates truly are near the second boundary -- e.g. roundtripping cftime.DatetimeNoLeap(2000, 1, 1, 0, 0, 0, 999999) with units of "days since 2000-01-01" -- but this is probably rarer than the issue in #187.

@jswhit
Copy link
Collaborator Author

jswhit commented Jul 17, 2020

Fix included for calculation of leap years when year is negative (issue #188). Closes issue #188.

Copy link
Collaborator

@spencerkclark spencerkclark left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fix included for calculation of leap years when year is negative

Good catch, thanks!

Jeff Whitaker and others added 2 commits July 18, 2020 13:13
Co-authored-by: Spencer Clark <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Back and forth conversions fail with num2date and date2num

3 participants