-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
time coding refactor #9906
time coding refactor #9906
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for splitting this off @kmuehlbauer—these changes look good. Just a few very minor questions.
@spencerkclark Thanks very much for the review. I've addressed according to your suggestions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
Co-authored-by: Spencer Clark <[email protected]>
for more information, see https://pre-commit.ci
Thanks @spencerkclark for the review. I think, I've addressed the review items. Planning to merge this early next week. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My brain hurts from trying to understand the differences between numpy and pandas times...
Thanks for the typing!
Thanks @headtr1ck for the review ❤️! |
This introduces some changes in the encoding/decoding pipeline to prepare for other units beside
ns
. It also fixes some inconsistencies wrt the exact ns.resolution datetime64 bounds.Finally it will reduce the "noise" over in #9618 quite substantial.
whats-new.rst