Bugfix 1460: preserve nanoseconds and timezones in date range from get info #1461
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
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.
THIS IS AN API CHANGE, AND SHOULD NOT BE MERGED UNTIL WE WANT TO BUMP THE MAJOR VERSION NUMBER FOR A MORE IMPORTANT FEATURE
Fixes #1460
Previously the
date_rangereturned byget_info[_batch]was adatetime.datetime, which only has microsecond precision.Now returns a
pandas.Timestampwith nanosecond precision.Also keeps the timezone information which was previously discarded for unknown reasons.