DOC: Corrections in Datetime Units-arrays.datetime.rst #7727
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Changed/corrected Time span - relative and absolute - for second, millisecond and microsecond. There were slight differences and was noted duly in the issue. See numpy#6711 (numpy#6711)
| us microsecond +/- 2.9e6 years [290301 BC, 294241 AD] | ||
| s second +/- 2.9e11 years [2.9e11 BC, 2.9e11 AD] | ||
| ms millisecond +/- 2.9e8 years [ 2.9e8 BC, 2.9e8 AD] | ||
| us microsecond +/- 2.9e5 years [290301 BC, 294241 AD] |
There was a problem hiding this comment.
Not sure of those dates, what with leap year and all, but probably close enough.
|
Thanks @badhrink . |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changed/corrected Time span - relative and absolute - for second, millisecond and microsecond.
There were slight differences in values and was noted duly in the issue. See #6711