-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
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: non-nano datetime64s for read_sas #56127
Conversation
doc/source/whatsnew/v2.2.0.rst
Outdated
@@ -188,6 +188,7 @@ Other enhancements | |||
- :meth:`to_sql` with method parameter set to ``multi`` works with Oracle on the backend | |||
- :attr:`Series.attrs` / :attr:`DataFrame.attrs` now uses a deepcopy for propagating ``attrs`` (:issue:`54134`). | |||
- :func:`read_csv` now supports ``on_bad_lines`` parameter with ``engine="pyarrow"``. (:issue:`54480`) | |||
- :func:`read_sas` returns ``datetime64`` dtypes with resolutions better matching those stored natively in SAS, and avoids returning object-dtype in cases that cannot be help with ``datetime64[ns]`` dtype (:issue:`56127`) |
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.
- :func:`read_sas` returns ``datetime64`` dtypes with resolutions better matching those stored natively in SAS, and avoids returning object-dtype in cases that cannot be help with ``datetime64[ns]`` dtype (:issue:`56127`) | |
- :func:`read_sas` returns ``datetime64`` dtypes with resolutions better matching those stored natively in SAS, and avoids returning object-dtype in cases that cannot be stored with ``datetime64[ns]`` dtype (:issue:`56127`) |
?
@@ -62,6 +58,10 @@ | |||
) | |||
|
|||
|
|||
_unix_origin = Timestamp("1970-01-01") |
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.
Will these be reused in the future? Otherwise could just inline the 10 year timedelta in _convert_datetimes
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.
either way. i think this is nicely clear about where the 10 year difference stems from (also cant do Timedelta(years=10))
Thanks @jbrockmendel |
doc/source/whatsnew/vX.X.X.rst
file if fixing a bug or adding a new feature.Pre-empts a bunch of the remaining test failures in #55901.
cc @ChadFulton for help determing what the correct "expected"s should be.