We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
utc=
Now that we support timezone aware types, we should properly handle the utc= argument:
In [3]: pd.to_datetime(['2001-01-01'], utc=True) Out[3]: DatetimeIndex(['2001-01-01 00:00:00+00:00'], dtype='datetime64[ns, UTC]', freq=None) In [4]: cudf.to_datetime(['2001-01-01'], utc=True) Out[4]: DatetimeIndex(['2001-01-01'], dtype='datetime64[ns]')
The text was updated successfully, but these errors were encountered:
Raise a NotImplementedError in to_datetime when utc is passed (#13670)
964925a
While we figure out a solution for #13661, this PR ensures that we correctly raise a `NotImplementedError`. Authors: - Ashwin Srinath (https://github.com/shwina) Approvers: - Matthew Roeschke (https://github.com/mroeschke) URL: #13670
Implement to_datetime(..., utc=True) (#14749)
d1c0e25
closes #13661 Also added typing and fixes a bug where `uint` data would raise a TypeError Authors: - Matthew Roeschke (https://github.com/mroeschke) Approvers: - Ashwin Srinath (https://github.com/shwina) URL: #14749
Successfully merging a pull request may close this issue.
Now that we support timezone aware types, we should properly handle the
utc=
argument:The text was updated successfully, but these errors were encountered: