-
-
Notifications
You must be signed in to change notification settings - Fork 19.1k
Bug: Grouping by index and column fails on DataFrame with single index (GH14327) #14428
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
Conversation
Current coverage is 85.26% (diff: 96.29%)@@ master #14428 diff @@
==========================================
Files 140 140
Lines 50639 50649 +10
Methods 0 0
Messages 0 0
Branches 0 0
==========================================
+ Hits 43177 43186 +9
- Misses 7462 7463 +1
Partials 0 0
|
@jreback it's green |
@jmmease can you make the doc-string updates. |
doc/source/whatsnew/v0.19.1.txt
Outdated
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.
say index level.
pandas/indexes/base.py
Outdated
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.
this should match the doc-string of the MultiIndex. ( best to use a shared_doc to avoid repeating doc-strings)
Existing logic under "if level is not None:" assumed that index was a MultiIndex. Now we check and also handle the case where an Index is passed in with a None grouper. This resolves GH 14327
…red_doc (GH 14327)
@jreback Made documentation updates and then rebased to resolve conflict in whatsnew 0.19.1. |
lgtm ping on green |
@jreback green |
@jmmease Thanks! |
…x (GH14327) (pandas-dev#14428) Existing logic under "if level is not None:" assumed that index was a MultiIndex. Now we check and also handle the case where an Index is passed in with a None grouper. This resolves GH 14327
git diff upstream/master | flake8 --diff
This PR is a continuation of #14333. See discussion there for explanation of why this new PR was needed.