REF: unify Index union methods #38382
Merged
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
jreback
requested changes
Dec 13, 2020
| expected = other | ||
| tm.assert_index_equal(result, expected) | ||
|
|
||
| other = empty_index(dtype="uint64", closed=closed) |
jreback
added
Index
jreback
approved these changes
Dec 14, 2020
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.
black pandasgit diff upstream/master -u -- "*.py" | flake8 --diffSits on top of #38373 which focuses on intersection.
@simonjayhawkins this changes corner-case behavior for IntervalIndex.union, which we already changed in #38282 for 1.2.0. I think this is unambiguously More Correct. Question for you: should we try to get it in to 1.2.0 to avoid back-to-back behavior changes?