BUG: Tuple subclasses should work as tuple in df.iloc[key]
#50625
Conversation
This file contains 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
|
This pull request is stale because it has been open for thirty days with no activity. Please update and respond to this comment if you're still interested in working on this. |
|
Thanks for the pull request, but it appears to have gone stale. If interested in continuing, please merge in the main branch, address any review comments and/or failing tests, and we can reopen. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
.ilocfails #48188doc/source/whatsnew/vX.X.X.rstfile if fixing a bug or adding a new feature.This patch makes tuple subclasses behave the same as tuple in
df.iloc[key]anddf.loc[key]. All but one of the tests pass. The failing test (indexing/test_loc.py::TestLocBaseIndependent::test_loc_getitem_index_namedtuple) raises an exception ondf.loc[key](not.iloc). I've opened issue #50597 where I suggest deprecating the behavior in that test. This patch would enforce that deprecation in addition to closing #48188.I'm opening this as is WIP but please comment. I have doubts on whether I'm on the right track with this.