@@ -272,9 +272,6 @@ parse_dates : boolean or list of ints or names or list of lists or dict, default
272272
273273 .. note ::
274274 A fast-path exists for iso8601-formatted dates.
275- infer_datetime_format : boolean, default ``False ``
276- If ``True `` and parse_dates is enabled for a column, attempt to infer the
277- datetime format to speed up the processing.
278275keep_date_col : boolean, default ``False ``
279276 If ``True `` and parse_dates specifies combining multiple columns then keep the
280277 original columns.
@@ -916,12 +913,11 @@ an exception is raised, the next one is tried:
916913
917914Note that performance-wise, you should try these methods of parsing dates in order:
918915
919- 1. Try to infer the format using ``infer_datetime_format=True `` (see section below).
920916
921- 2 . If you know the format, use ``pd.to_datetime() ``:
917+ 1 . If you know the format, use ``pd.to_datetime() ``:
922918 ``date_parser=lambda x: pd.to_datetime(x, format=...) ``.
923919
924- 3 . If you have a really non-standard format, use a custom ``date_parser `` function.
920+ 2 . If you have a really non-standard format, use a custom ``date_parser `` function.
925921 For optimal performance, this should be vectorized, i.e., it should accept arrays
926922 as arguments.
927923
@@ -1651,7 +1647,6 @@ Options that are unsupported by the pyarrow engine which are not covered by the
16511647* ``decimal ``
16521648* ``iterator ``
16531649* ``dayfirst ``
1654- * ``infer_datetime_format ``
16551650* ``verbose ``
16561651* ``skipinitialspace ``
16571652* ``low_memory ``
0 commit comments