BUG: Join did not work correctly when one MultiIndex had only one level #37208
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
Contributor
|
This pull request is stale because it has been open for thirty days with no activity. Please update or respond to this comment if you're still interested in working on this. |
jreback
requested changes
Jan 1, 2021
doc/source/whatsnew/v1.2.0.rst
Outdated
| - Bug in func :meth:`crosstab` when using multiple columns with ``margins=True`` and ``normalize=True`` (:issue:`35144`) | ||
| - Bug in :meth:`DataFrame.agg` with ``func={'name':<FUNC>}`` incorrectly raising ``TypeError`` when ``DataFrame.columns==['Name']`` (:issue:`36212`) | ||
| - Bug in :meth:`Series.transform` would give incorrect results or raise when the argument ``func`` was dictionary (:issue:`35811`) | ||
| - Bug in :func:`join` over :class:`MultiIndex` returned wrong result, when one of both indexes had only one level (:issue:`36909`) |
� Conflicts: � doc/source/whatsnew/v1.2.0.rst � pandas/core/indexes/base.py � pandas/tests/indexes/multi/test_drop.py � pandas/tests/reshape/merge/test_join.py
Member
Author
|
Done |
jreback
requested changes
Jan 3, 2021
| tm.assert_frame_equal(result, expected) | ||
|
|
||
|
|
||
| @pytest.mark.parametrize("how", ["left", "right", "inner", "outer"]) |
Contributor
There was a problem hiding this comment.
don't we have a fixture for this?
pandas/core/indexes/base.py
Outdated
| """ | ||
|
|
||
| if not levnums: | ||
| if not levnums and (len(self) > 1 or not isinstance(self, ABCMultiIndex)): |
Contributor
There was a problem hiding this comment.
this len(self) > 1 is a very odd check, what is the intent?
Member
Author
There was a problem hiding this comment.
Seems to be no longer necessary. Code changed quite a bit since I implemented this. Removed it.
� Conflicts: � doc/source/whatsnew/v1.3.0.rst
jreback
approved these changes
Jan 3, 2021
Member
Author
|
@jreback green |
Contributor
|
thanks |
luckyvs1
pushed a commit
to luckyvs1/pandas
that referenced
this pull request
Jan 20, 2021
…el (pandas-dev#37208) * BUG: join did not work correctly when one MultiIndex had only one level * Change pr number * Move whatsnew * Remove pd * Usef fixture * Remove len self
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.
black pandasgit diff upstream/master -u -- "*.py" | flake8 --diffdroplevelforMultiIndexreturns anIndexwhen the resultingMultiIndexhad only one level. But if the input had only one level and no level should be dropped, the return was aMultiIndex. This did not seem consistent, so I changed it, that in this case an Index would be returned too. If this is not the desired behavior, we could fix thejoinproblems after calling this functions.If this is not desired, we should add a note to the docstring, that the return for
droplevelis a MultiIndex, if no level is dropped.