-
Notifications
You must be signed in to change notification settings - Fork 915
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
Restrict the allowed pandas timezone objects in cudf #16013
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.
Minor queries, and one name-typo fix.
from cudf.core.column.timedelta import TimeDeltaColumn | ||
|
||
|
||
def get_compatable_timezone(dtype: pd.DatetimeTZDtype) -> pd.DatetimeTZDtype: |
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.
def get_compatable_timezone(dtype: pd.DatetimeTZDtype) -> pd.DatetimeTZDtype: | |
def get_compatible_timezone(dtype: pd.DatetimeTZDtype) -> pd.DatetimeTZDtype: |
et seq., throughout
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 the catch!
Looks like we're back to 91% as of 413690d
|
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 @mroeschke
/merge |
Description
Since cudf's timezone support is based on the OS's tz data and hence
zoneinfo
, cudf cannot naturally support the variety of timezone objects supported by pandas (pytz
,dateutil
, etc). Therefore:pytz.timezone("US/Pacific")
->zoneinfo.ZoneInfo("US/Pacific")
Checklist