FIX-#7669: Respect eval(inplace=False). #7670
Merged
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.
Prior to this commit, calling
DataFrame.eval(inplace=False, engine='python')
with an assignment would incorrectly update the input dataframe. The root cause was callingcopy(deep=None)
instead ofcopy(deep=True)
. We need to insert new columns to a deep copy of the input dataframe.deep=None
is not part of thecopy
API at all, so we don't need to fixcopy()
behavior. It happens thatdeep=None
does a deep copy in pandas, which is where we got thedeep=None
code from.Resolves #7669