-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
ENH: Add dtype_backend parameter to to_datetime #53952
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
Yep this sounds good. Same as for to_numeric basically. Pinging @MarcoGorelli |
sounds good - interested in submitting a pull request @wirable23 ? |
@MarcoGorelli yes! The issue I was facing was that I didn't see arrow compute functions for some functionality of to_datetime, for example, pyarrow does not seem to have a compute function for creating datetimes from day month year components. Also, pyarrow does not support casting floating points to datetimes but there might be some other compute function that can be used. |
@lithomas1 @wirable23 I see there haven't been any updates to this issue in a while. |
Go for it. |
take |
I initially assigned myself as I thought I had a good idea of how this should be implemented, however after looking more deeply into to_datetime and pyarrow, I realize that I might've bit off more than I could chew... My main issue is trying to figure out the best places to convert the dates between their numpy and pyarrow counterparts. Therefore, I will be unassigning myself from this issue. I apologize for any inconvenience caused! |
Feature Type
Adding new functionality to pandas
Changing existing functionality in pandas
Removing existing functionality in pandas
Problem Description
In the above example, passing in a pyarrow backed series to to_datetime returns a numpy backed series, in to_numeric, there's a dtype_backend parameter that allows preserving of pyarrow dtypes, it would be nice to have the same option in to_datetime.
Feature Description
Same way as in to_numeric, adding a dtype_backend parameter.
Alternative Solutions
N/A
Additional Context
No response
The text was updated successfully, but these errors were encountered: