-
-
Notifications
You must be signed in to change notification settings - Fork 19.3k
BUG: DataFrameGroupBy.quantile raises for non-numeric dtypes rather than dropping columns #34756
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
|
looks like you are including the changes in #34372 here as well |
794788d to
9f379ac
Compare
| tm.assert_series_equal(result, expected) | ||
|
|
||
|
|
||
| @pytest.mark.parametrize("q", [0.5, [0.0, 0.5, 1.0]]) |
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.
can you also try with an empty frame that has the same dtypes, that should raise?
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.
It does not raise on an empty frame, but instead returns an empty frame with the columns that are valid dtypes, in the case of the test Columns: [b].
|
@rhshadrach merging master should fix the CI failure. |
3b39fc0 to
441d251
Compare
|
@jreback - the response never updated but Travis passed. Responses to your questions are above. |
|
Accidentally deleted PR branch |
|
@jreback Friendly ping. Responses to your questions are above. |
|
thanks @rhshadrach |
black pandasgit diff upstream/master -u -- "*.py" | flake8 --diffUnlike what is mentioned in #27892, this will raise if there are no columns to aggregate. Both mean and median raise with "No numeric types to aggregate" in such a case, so I was thinking perhaps we should be consistent with them. Any thoughts @WillAyd and @TomAugspurger?