-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
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
ENH: initial support for non-nano Timestamp #46839
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.
So just to confirm, this PR just allows preserving the resolution from np.datetime64
objects? Do you have plans to support passing in resolution from the Timestamp
constructor too?
Correct. This way I can incrementally implement tests for tznaive cases, then expand to tzaware cases, etc.
Yes, though the exact API is still up in the air (xref #46587). On last week's dev call we were leaning towards a new keyword, though im still reticent, so punting on this for the time being. |
# Constructors | ||
|
||
@classmethod | ||
def _from_dt64(cls, dt64: np.datetime64): |
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.
ideally can return type (followon)
doc/source/whatsnew/vX.X.X.rst
file if fixing a bug or adding a new feature.