TST: add copy/view test for setting columns with an array/series #47070
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
jorisvandenbossche
added
Testing
|
Yes, should be fixed now! |
jreback
approved these changes
May 21, 2022
| def test_set_column_with_series(using_copy_on_write): | ||
| # Case: setting a series as a new column (df[col] = s) copies that data | ||
| df = DataFrame({"a": [1, 2, 3], "b": [4, 5, 6]}) | ||
| s = Series([1, 2, 3]) |
| assert not np.shares_memory(df["c"].values, s.values) | ||
|
|
||
| # and modifying the series does not modify the DataFrame | ||
| s.iloc[0] = 0 |
There was a problem hiding this comment.
could also assert s.iloc[0] == 0, as failure for that to hold would be another way the next assertion could pass
|
nitpicks, otherwise LGTM. i really liked the comments @jorisvandenbossche ! |
mroeschke
approved these changes
May 21, 2022
|
Thanks @jorisvandenbossche |
yehoshuadimarsky
pushed a commit
to yehoshuadimarsky/pandas
that referenced
this pull request
Jul 13, 2022
…das-dev#47070) * TST: add copy/view test for setting columns with an array/series * Update pandas/tests/copy_view/test_setitem.py * address feedback
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.
Similarly as #46979, this is adding some test cases explicitly testing copy/view behaviour for a specific topic: if we set an array or series as a column, is the new column a copy or a view of the original data?
At this moment, we actually already do make a copy of that data (with one exception being the cached RangeIndex values). So the tests I added here are confirming that current behaviour in tests, and adding a few checks where Copy-on-Write could delay the copy.