You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After #55901, to_datetime with strings will now infer the resolution from the data, but the related pd.date_range to create datetime data still returns nanoseconds:
Should we update pd.date_range as well to infer the resulting resolution from the start/stop timestamp and freq ?
(I encountered this inconsistency in the pyarrow tests, where we essentially were using both idioms to create a result and expected data, but so that started failing because of a different dtype. I also opened #58989 for that, but regardless of a possible default resolution, pd.date_range would still need to follow that as well)
The text was updated successfully, but these errors were encountered:
After #55901,
to_datetime
with strings will now infer the resolution from the data, but the relatedpd.date_range
to create datetime data still returns nanoseconds:Should we update
pd.date_range
as well to infer the resulting resolution from the start/stop timestamp and freq ?(I encountered this inconsistency in the pyarrow tests, where we essentially were using both idioms to create a result and expected data, but so that started failing because of a different dtype. I also opened #58989 for that, but regardless of a possible default resolution,
pd.date_range
would still need to follow that as well)The text was updated successfully, but these errors were encountered: