Skip to content

Commit 3c9d86c

Browse files
committed
whatsnew doc about changed integer conversion
1 parent dae93d2 commit 3c9d86c

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

doc/source/whatsnew/v3.0.0.rst

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -374,6 +374,8 @@ In cases with mixed-resolution inputs, the highest resolution is used:
374374
In [2]: pd.to_datetime([pd.Timestamp("2024-03-22 11:43:01"), "2024-03-22 11:43:01.002"]).dtype
375375
Out[2]: dtype('<M8[ns]')
376376
377+
Many users will now get "M8[us]" dtype data in cases when they used to get "M8[ns]". For most use cases they should not notice a difference. One big exception is converting to integers, which will give integers 1000x smaller.
378+
377379
.. _whatsnew_300.api_breaking.value_counts_sorting:
378380

379381
Changed behavior in :meth:`DataFrame.value_counts` and :meth:`DataFrameGroupBy.value_counts` when ``sort=False``

0 commit comments

Comments
 (0)