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/v1.2.0.rst
+7
Original file line number
Diff line number
Diff line change
@@ -309,6 +309,13 @@ Optional libraries below the lowest tested version may still work, but are not c
309
309
310
310
See :ref:`install.dependencies` and :ref:`install.optional_dependencies` for more.
311
311
312
+
.. _whatsnew_200.api.other:
313
+
314
+
Other API changes
315
+
^^^^^^^^^^^^^^^^^
316
+
317
+
- Sorting in descending order is now stable for :meth:`Series.sort_values` and :meth:`Index.sort_values` for DateTime-like :class:`Index` subclasses. This will affect sort order when sorting :class:`DataFrame` on multiple columns, sorting with a key function that produces duplicates, or requesting the sorting index when using :meth:`Index.sort_values`. When using :meth:`Series.value_counts`, count of missing values is no longer the last in the list of duplicate counts, and its position corresponds to the position in the original :class:`Series`. When using :meth:`Index.sort_values` for DateTime-like :class:`Index` subclasses, NaTs ignored the ``na_position`` argument and were sorted to the beggining. Now they respect ``na_position``, the default being ``last``, same as other :class:`Index` subclasses. (:issue:`35992`)
0 commit comments