TST: Add SparseArray _arith_method test to fail on incorrect comparison operator #59648
Conversation
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
|
@mroeschke Could you take a look at the change? Thanks! |
mroeschke
reviewed
Aug 29, 2024
mroeschke
added
Testing
mroeschke
approved these changes
Aug 31, 2024
|
Thanks @jsngn |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Added type annotations to new arguments/methods/functions.Not applicableAdded an entry in the latestNot applicabledoc/source/whatsnew/vX.X.X.rstfile if fixing a bug or adding a new feature.Before, if the line core/arrays/sparse/array.py:1768 is changed from
if len(self) != len(other):toif len(self) > len(other):, all tests still passed. Now they will fail if the comparison operator is changed to anything besides!=.