-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
to_datetime loses freq on DatetimeIndex with offset #6562
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
Comments
Timestamp no longer accepts the offset keyword (deprecated and removed). Closing. |
@mroeschke I think this is still an issue with the
|
Oh I see. I had also rationalized closing this in light of #15146, but I see you mentioned that removing freq from Timestamp is non-trivial. Do you believe that's still the case? |
Backwards-compat would be annoying, not sure if anyone would really complain though. Getting rid of it would break a behavior that is nice for testing that But as long as the attribute does exist, I think |
Sounds good. Reopening. |
@mroeschke didn't this get solved recently? |
This now works for the scalar case but still not the array case. But should the
|
This was once closed and then reopened due to |
It would be cool if the offset were kept. Perhaps even an error should be raised if not all of the
Timestamp
s have the sameoffset
:See #6560
The text was updated successfully, but these errors were encountered: