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
PERF: Do not init cache in RangeIndex.take (#53397)
* PERF: Do not init cache in RangeIndex.take
Improve performance when passing an array to RangeIndex.take, DataFrame.loc, or DataFrame.iloc and the DataFrame is using a RangeIndex
* Explicitly raise ValueError in RangeIndex.take when allow_fill is True and fill_value is not None
* Add test_take_when_index_has_negative_step
* Override RangeIndex._find_common_type_compat
* Revert "Override RangeIndex._find_common_type_compat"
This reverts commit 102644c.
* Change find_result_type to take a dtype instead of values
* Call _maybe_disallow_fill
* Move checks from test_cache_after_calling_loc_with_array to test_cache
Copy file name to clipboardExpand all lines: doc/source/whatsnew/v2.1.0.rst
+1
Original file line number
Diff line number
Diff line change
@@ -412,6 +412,7 @@ Performance improvements
412
412
- Performance improvement in various :class:`MultiIndex` set and indexing operations (:issue:`53955`)
413
413
- Performance improvement when doing various reshaping operations on :class:`arrays.IntegerArrays` & :class:`arrays.FloatingArray` by avoiding doing unnecessary validation (:issue:`53013`)
414
414
- Performance improvement when indexing with pyarrow timestamp and duration dtypes (:issue:`53368`)
415
+
- Performance improvement when passing an array to :meth:`RangeIndex.take`, :meth:`DataFrame.loc`, or :meth:`DataFrame.iloc` and the DataFrame is using a RangeIndex (:issue:`53387`)
0 commit comments