-
Notifications
You must be signed in to change notification settings - Fork 13.3k
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
Nanosecond timestamp year range workaround #900
Labels
enhancement:request
Enhancement request submitted by anyone from the community
Comments
xrmx
added
the
enhancement:request
Enhancement request submitted by anyone from the community
label
Aug 9, 2016
Notice: this issue has been closed because it has been inactive for 621 days. Feel free to comment and request for this issue to be reopened. |
Throws (default): pd.to_datetime(datetime.date(2262, 4, 12),errors='raise') any chance we could change this to coerce? |
zhaoyongjie
pushed a commit
to zhaoyongjie/incubator-superset
that referenced
this issue
Nov 17, 2021
zhaoyongjie
pushed a commit
to zhaoyongjie/incubator-superset
that referenced
this issue
Nov 24, 2021
zhaoyongjie
pushed a commit
to zhaoyongjie/incubator-superset
that referenced
this issue
Nov 25, 2021
zhaoyongjie
pushed a commit
to zhaoyongjie/incubator-superset
that referenced
this issue
Nov 26, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, pd timestamps are restricted to the years 1677-2262. It would be nice to allow different dates as well that go beyond this range. For instance, periodranges could be an alternative. That would allow graphing of longer timeseries plots.
The text was updated successfully, but these errors were encountered: