BUG: Fix DataFrame.eval to return scalar for string literal with in/not in operators#65037
Open
deniskrds wants to merge 3 commits intopandas-dev:mainfrom
Open
BUG: Fix DataFrame.eval to return scalar for string literal with in/not in operators#65037deniskrds wants to merge 3 commits intopandas-dev:mainfrom
in/not in operators#65037deniskrds wants to merge 3 commits intopandas-dev:mainfrom
Conversation
deniskrds
changed the title
in/not in operators
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.
evalnot working with string containment #64391doc/source/whatsnew/v3.1.0.rstfile if fixing a bug or adding a new feature.AGENTS.md.df.eval('"foo" in value')returnedSeries([False, False, ...])instead of a scalar boolean.The root cause was
_rewrite_membership_opwrapping the string literal "foo" into ["foo"], causing Series.isin(["foo"]) to run — an exact equality check that always returned False for non-exact matches.Fix applied as skipping the wrapping when the operator is already in/not in, so it falls through to Python's native x in y semantics and returns a scalar correctly.