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
Copy file name to clipboardExpand all lines: doc/source/whatsnew/v0.17.0.txt
+43-3
Original file line number
Diff line number
Diff line change
@@ -65,10 +65,11 @@ Other enhancements
65
65
- Enable `read_hdf` to be used without specifying a key when the HDF file contains a single dataset (:issue:`10443`)
66
66
67
67
- ``DatetimeIndex`` can be instantiated using strings contains ``NaT`` (:issue:`7599`)
68
-
- The string parsing of ``to_datetime``, ``Timestamp`` and ``DatetimeIndex`` has been made consistent" (:issue:`7599`)
68
+
- The string parsing of ``to_datetime``, ``Timestamp`` and ``DatetimeIndex`` has been made consistent. (:issue:`7599`)
69
69
70
-
Prior to v0.17.0, ``Timestamp`` and ``to_datetime`` may parse year-only datetime-string incorrectly using today's date, otherwise ``DatetimeIndex`` uses the beginning of the year.
71
-
``Timestamp`` and ``to_datetime`` may raise ``ValueError`` in some types of datetime-string which ``DatetimeIndex`` can parse, such as quarterly string.
70
+
Prior to v0.17.0, ``Timestamp`` and ``to_datetime`` may parse year-only datetime-string incorrectly using today's date, otherwise ``DatetimeIndex``
71
+
uses the beginning of the year. ``Timestamp`` and ``to_datetime`` may raise ``ValueError`` in some types of datetime-string which ``DatetimeIndex``
72
+
can parse, such as a quarterly string.
72
73
73
74
Previous Behavior
74
75
@@ -121,6 +122,45 @@ Backwards incompatible API changes
121
122
122
123
- Line and kde plot with ``subplots=True`` now uses default colors, not all black. Specify ``color='k'`` to draw all lines in black (:issue:`9894`)
123
124
125
+
.. _whatsnew_0170.api_breaking.to_datetime
126
+
127
+
Changes to to_datetime and to_timedelta
128
+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
129
+
130
+
The default for ``pd.to_datetime`` error handling has changed to ``errors='raise'``. In prior versions it was ``errors='ignore'``.
131
+
Furthermore, the ``coerce`` argument has been deprecated in favor of ``errors='coerce'``. This means that invalid parsing will raise rather that return the original
0 commit comments