Skip to content

Commit 77801e0

Browse files
committed
Whatsnew
1 parent 69537b2 commit 77801e0

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

doc/source/whatsnew/v3.0.0.rst

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -354,7 +354,7 @@ When passing strings, the resolution will depend on the precision of the string,
354354
In [5]: pd.to_datetime(["2024-03-22 11:43:01.002003004"]).dtype
355355
Out[5]: dtype('<M8[ns]')
356356
357-
The inferred resolution now matches that of the input strings:
357+
The inferred resolution now matches that of the input strings for nanosecond-precision strings, otherwise defaulting to microseconds:
358358

359359
.. ipython:: python
360360
@@ -363,6 +363,8 @@ The inferred resolution now matches that of the input strings:
363363
In [4]: pd.to_datetime(["2024-03-22 11:43:01.002003"]).dtype
364364
In [5]: pd.to_datetime(["2024-03-22 11:43:01.002003004"]).dtype
365365
366+
This is also a change for the :class:`Timestamp` constructor with a string input, which in version 2.x.y could give second or millisecond unit, which users generally disliked (:issue:`52653`)
367+
366368
In cases with mixed-resolution inputs, the highest resolution is used:
367369

368370
.. code-block:: ipython

0 commit comments

Comments
 (0)