-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
BUG: partially-inferring pydatetime objects #44296
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
Conversation
jbrockmendel
commented
Nov 2, 2021
•
edited by jreback
Loading
edited by jreback
- xref API/BUG: partially-inferring datetimes #40111
- tests added / passed
- Ensure all linting tests pass, see here for how to run them
- whatsnew entry
) | ||
tm.assert_series_equal(mixed, expected) |
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.
does this PR fully close the issue? The issue refers to this as not being idempotent.
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.
can keep it open with a comment that the idempotency has not been addressed
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.
sgtm
with pytest.raises(ValueError, match="Tz-aware datetime.datetime"): | ||
to_datetime(ser) | ||
to_datetime(mixed) |
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.
this second call to to_datetime
should be a no-op?
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.
likely; treating that as separate
cc @mroeschke if any comments |