docs: showed warning

Author: Shashwat

doc/source/user_guide/io.rst

@@ -272,6 +272,12 @@ parse_dates : boolean or list of ints or names or list of lists or dict, default
 
   .. note::
      A fast-path exists for iso8601-formatted dates.
+
+  .. note::
+   The ``infer_datetime_format`` is deprecated and will be removed in the future versions. 
+infer_datetime_format : boolean, default ``False``
+  If ``True`` and parse_dates is enabled for a column, attempt to infer the
+  datetime format to speed up the processing.(this is deprecated and will be removed in a future version)
 keep_date_col : boolean, default ``False``
   If ``True`` and parse_dates specifies combining multiple columns then keep the
   original columns.
@@ -913,11 +919,12 @@ an exception is raised, the next one is tried:
 
 Note that performance-wise, you should try these methods of parsing dates in order:
 
+1. Try to infer the format using ``infer_datetime_format=True`` (this is deprecated and will be removed in the future versions.).
 
-1. If you know the format, use ``pd.to_datetime()``:
+2. If you know the format, use ``pd.to_datetime()``:
    ``date_parser=lambda x: pd.to_datetime(x, format=...)``.
 
-2. If you have a really non-standard format, use a custom ``date_parser`` function.
+3. If you have a really non-standard format, use a custom ``date_parser`` function.
    For optimal performance, this should be vectorized, i.e., it should accept arrays
    as arguments.
 
@@ -1647,6 +1654,7 @@ Options that are unsupported by the pyarrow engine which are not covered by the
 * ``decimal``
 * ``iterator``
 * ``dayfirst``
+* ``infer_datetime_format``
 * ``verbose``
 * ``skipinitialspace``
 * ``low_memory``
@@ -6378,4 +6386,4 @@ The files ``test.pkl.compress``, ``test.parquet`` and ``test.feather`` took the
     24009288 Oct 10 06:43 test_fixed.hdf
     24009288 Oct 10 06:43 test_fixed_compress.hdf
     24458940 Oct 10 06:44 test_table.hdf
-    24458940 Oct 10 06:44 test_table_compress.hdf
+    24458940 Oct 10 06:44 test_table_compress.hdf