-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
Fix Issue #21336: Defeault behavior for resolution property in Timestamps #21365
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
Changes from 2 commits
cadd955
5fdfd9e
544e834
a72e434
b7caafb
83c73da
c53f2c2
62705aa
74eb1a3
3638889
75e4a85
1c63c2a
651a8e4
0e9e461
f28dc5d
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -116,3 +116,4 @@ Other | |
|
||
- Tab completion on :class:`Index` in IPython no longer outputs deprecation warnings (:issue:`21125`) | ||
- Bug preventing pandas from being importable with -OO optimization (:issue:`21071`) | ||
- Timestamp resolution returns a :class:`Timedelta` rather than a normal `timedelta` object (:issue:`21336`) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think the main point of the issue was that before the stated resolution was 1 microsecond while in actuality its 1 nanosecond (but we can't use There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Resolved in commit c53f2c2 |
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.
Looks like this already in the
**Other Fixes**
section.