-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
BUG: Series.where not casting None to nan #39761
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
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
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
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.
What the general rationale to decide which tests go in
/tests/indexing
and which in/tests/series/indexing
?Here, it are tests that have a Series version and a DataFrame version (just below here). Since those tests are very similar, IMO it makes sense to keep them together?
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.
Some of this is laid out in test_writing.rst. There is no doubt room for improvement in that file if you have suggestions.
The over-arching MO is to organize indexing tests by method. So anything for
Series.__setitem__
would go in tests/series/indexing/test_setitem.py. Under this theory, all of tests(/frame|/series)?/indexing/test_indexing.py files and all of the tests(/frame|/series)?/indexing/test_{dtype}.py files would eventually have their tests moved to a method-specific file. Many of the remaining tests in these files are hard to categorize as being for a single method, so do not (yet?) conform to this pattern.The MO specific to this PR and recent similar ones is to get more
Series.__setitem__
tests to useSetitemCastingEquivalents
which is proving very useful for finding inconsistencies. This cuts against the method-specific organization so the final location of it may be reconsidered at some point.I expect we will either extend SetitemCastingEquivalents to include DataFrame cases or implement similar classes that handle cases SetitemCastingEquivalents can't.