-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
CLN: enforce deprecation of the method
keyword on df.fillna
#57760
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
Merged
mroeschke
merged 9 commits into
pandas-dev:main
from
natmokval:cln-enforce-deprecation-of-param-method-in-fillna
Mar 14, 2024
Merged
Changes from 8 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
ddbe93b
enforce deprecation of param method in df.fillna: correct def fillna,…
natmokval 9412e7f
correct def fillna, fix tests
natmokval a326ff3
correct an example in v0.10.0, fix test
natmokval 72a30a7
add a note to v3.0.0
natmokval 8567e49
remove an entry from ignored_doctest_warnings
natmokval d14fdb2
fix pylint error in test_sparse.py
natmokval d452f62
correct fillna docstring
natmokval c6490a2
correct fillna docstring II
natmokval c570619
correct tests
natmokval 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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
Could you check if we have a test where
value
is anp.array
orpd.Series
? Given the error message, I would expect this check to be something likeif not (is_scalar(value) or isinstance(value, dict))
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.
we have
test_fillna_series
inpandas/tests/extension/base/missing.py
where we fill with a seriespandas/pandas/tests/extension/base/missing.py
Lines 123 to 141 in 3132971
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.
in
pandas/tests/frame/methods/test_fillna.py
I foundtest_fillna_invalid_value
.pandas/pandas/tests/frame/methods/test_fillna.py
Lines 563 to 577 in 97c31a6
In this test we check if for value:
list, tuple or DataFrame
fillna raisesTypeError
.We don't validate values:
np.array and Series
in this tests though. I checked, for examples belowwe get the TypeError:
TypeError: "value" parameter must be a scalar, dict or Series, but you passed a "ndarray"
Should I add a check for
np.array
and maybe correct the condition inif
statement?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.
Thanks for looking! Since we have a test with
np.array
and check that we're raising the error correctly so no need to add the check