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
Steps/Code to reproduce bug
In [1]: import pandas as pd In [2]: import cudf In [3]: pd.Timestamp(123) Out[3]: Timestamp('1970-01-01 00:00:00.000000123') In [4]: s = pd.Timestamp(123) In [5]: ser = cudf.Series(s) In [6]: ser Out[6]: 0 1970-01-01 00:00:00.000000123 dtype: datetime64[ns] In [7]: ser = cudf.Series([s]) In [8]: ser Out[8]: 0 1970-01-01 dtype: datetime64[us] In [9]: pd.Series(s) Out[9]: 0 1970-01-01 00:00:00.000000123 dtype: datetime64[ns] In [10]: pd.Series([s]) Out[10]: 0 1970-01-01 00:00:00.000000123 dtype: datetime64[ns]
Expected behavior Same as pandas
Environment overview (please complete the following information)
The text was updated successfully, but these errors were encountered:
Preserve sub-second data for time scalars in column construction (#15655
5d244df
) Fixes: #15654 This PR makes fixes such that sub-second timestamp data is not being dropped in column construction. Forks out of #14534 Authors: - GALI PREM SAGAR (https://github.com/galipremsagar) Approvers: - Matthew Roeschke (https://github.com/mroeschke) URL: #15655
galipremsagar
Successfully merging a pull request may close this issue.
Steps/Code to reproduce bug
Expected behavior
Same as pandas
Environment overview (please complete the following information)
The text was updated successfully, but these errors were encountered: