FIX: Preserve dtypes when using scalar row + slice columns indexing #63081
+45
−29
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR fixes an issue where using scalar row + slice columns indexing (e.g.
df[scalar_row, slice_columns]) would not preserve column dtypes properly. The fix implements a special case for this indexing pattern to first extract the column slice, preserving dtypes, then extract the specific row.Checklist
Proof
The fix addresses issue #63071 by handling the scalar row + slice columns case specifically in
_LocationIndexer._getitem_lowerdim. The solution first gets the column slice to create a sub-DataFrame with preserved column dtypes, then extracts the required row from this sub-DataFrame. This ensures that the resulting Series maintains the original column dtypes as expected.Closes #63071