BUG: fix #59950 handle duplicate column names in dataframe queries #59971
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.
Issue Description
When calling
DataFrame.query()
on a DataFrame with duplicate column names, an unexpectedTypeError
is raised due to a change introduced in pandas 2.2.1. The root cause is theself.dtypes[k]
returning a Series for duplicate column names instead of a single value, leading to a failure in the query evaluation.Changes Made
Fixed an issue where
Dataframe.query()
would throw an unexpected errorThe error was caused by
self.dtypes[k]
Adjusted the behavior to match the behavior prior to pandas version
Added tests to ensure that
Dataframe.query()
works as expectedPR Checklist
doc/source/whatsnew/vX.X.X.rst
file if fixing a bug or adding a new feature.