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
BUG: do not raise UnsortedIndexError if sorting is not required
closes#16734
Author: Pietro Battiston <me@pietrobattiston.it>
This patch had conflicts when merged, resolved by
Committer: Jeff Reback <jeff.reback@twosigma.com>
Closes#16736 from toobaz/index_what_you_can and squashes the following commits:
f77e2b3 [Pietro Battiston] BUG: do not raise UnsortedIndexError if sorting is not required
Copy file name to clipboardExpand all lines: doc/source/whatsnew/v0.21.0.txt
+1
Original file line number
Diff line number
Diff line change
@@ -99,6 +99,7 @@ Indexing
99
99
^^^^^^^^
100
100
101
101
- When called with a null slice (e.g. ``df.iloc[:]``), the ``.iloc`` and ``.loc`` indexers return a shallow copy of the original object. Previously they returned the original object. (:issue:`13873`).
102
+
- When called on an unsorted ``MultiIndex``, the ``loc`` indexer now will raise ``UnsortedIndexError`` only if proper slicing is used on non-sorted levels (:issue:`16734`).
0 commit comments