ENH: Allow Arrow types directly with pd.to_datetime

[WillAyd]

ENH: Allow Arrow types directly with pd.to_datetime

[jbrockmendel]

I'm very skeptical of making pd.to_datetime more complicated (both as an API and the implementation).

pd.to_datetime(ser).dt.to_period("D") is effectively a date dtype.

Alternately maybe we need to introduce a new pd.to_date

Side-note: I've been kicking around the idea of a pd.to.foo namespace to collect all of the to_foo functions, since the top-level namespace is pretty big. ATM to_offset and to_time are buried and could be included.

[mroeschke]

to_numeric had a dtype_backend keyword added in 2.0 IIRC. I wouldn't be opposed to adding that keyword to to_datetime for symmetry but return pa.timestamp types and not pa.date types.

[jbrockmendel]

I wasnt aware of the keyword in to_numeric; I would have been -0.75 on that.

In to_datetime it has the added downside of complicating the return type (not just dtype). The base case to_datetime returns a DatetimeIndex. A keyword would change that to be a base class Index.

.convert_dtypes already works for the timestamp dtypes. One Obvious Way.

[WillAyd]

I also think dtype_backend here is a partial solution that doesn't necessarily clarify how to accomplish the task the best way.

pd.to_datetime(ser).dt.to_period("D") is effectively a date dtype.

That's in interesting idea but I think would be really tough to roundtrip and use effectively with our I/O

AFAIU the only way to specifically get a non-object date in this case is to ser.astype(pd.ArrowDtype(pa.date32())) - is that correct?

[mroeschke]

AFAIU the only way to specifically get a non-object date in this case is to ser.astype(pd.ArrowDtype(pa.date32())) - is that correct?

Correct

[mroeschke]

.convert_dtypes already works for the timestamp dtypes. One Obvious Way.

This is a good point. to_numeric with dtype_backend="pyarrow" essentially astypes from nullable numpy types to arrow types which is covered by convert_dtypes