-
- Notifications
You must be signed in to change notification settings - Fork 19.3k
BUG: don't assume series is length > 0 #19438
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from 1 commit
Commits
Show all changes
13 commits Select commit Hold shift + click to select a range
6bd6ddd BUG: don't assume series is length > 0
hexgnu 7fdd03e Take out comment and use product
hexgnu 27df317 Merge remote-tracking branch 'upstream/master' into segfault_memory_u…
hexgnu e251587 Fix failing test with indexing
hexgnu 5e59e9c Use range over 0 <= for loops
hexgnu 3f52a44 Ah ha I think I got it
hexgnu 21ae147 FIX: revert change to lib.pyx
hexgnu 207bc74 Define memory_usage on SparseArray
hexgnu 93a0c3d Merge remote-tracking branch 'upstream/master' into segfault_memory_u…
hexgnu cdd4141 Fix linting error
hexgnu ae9f74d Revert base.py
hexgnu 4ead141 Move whatsnew doc to Sparse
hexgnu f9433d8 Use shared docstring and get rid of if condition
hexgnu File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| | @@ -971,6 +971,17 @@ def test_combine_first(self): | |
| tm.assert_sp_series_equal(result, result2) | ||
| tm.assert_sp_series_equal(result, expected) | ||
| | ||
| @pytest.mark.parametrize('deep,fill_values', [([True, False], | ||
| [0, 1, np.nan, None])]) | ||
| def test_memory_usage_deep(self, deep, fill_values): | ||
| for fv in fill_values: | ||
| ||
| sparse_series = SparseSeries(fill_values, fill_value=fv) | ||
| dense_series = Series(fill_values) | ||
| sparse_usage = sparse_series.memory_usage(deep=deep) | ||
| dense_usage = dense_series.memory_usage(deep=deep) | ||
| | ||
| assert sparse_usage < dense_usage | ||
| | ||
| | ||
| class TestSparseHandlingMultiIndexes(object): | ||
| | ||
| | ||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do you think this is the issue?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is ok, I think are definition of memory_usage should be slightly updated. (in core/base.py) as its meant for pure object dtypes, not sparse.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should it be updated?
My understanding is that memory_usage for a SparseSeries should equal to the memory_usage of the index plus the memory_usage of the SparseArray
The original bug is honestly an edgecase because if you have more than one dense element it doesn't fail:
I'm not sure core/base.py should be updated. The problem with doing that would be that I would do a length check before handing it off to the lower level pyx file. This fix gets rid of the possible segfault by accessing memory that's not there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also I meant to take out my thought process comment ;). I'll do that now