-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
BUG: add reset logic for Grouper if new obj is passed in (#26564) #29800
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
needs tests that the relevant bug is fixed |
this PR is likely duplicating this one: #29131 |
@jreback I wrote a test here and ran it against #29131 which doesn't pass the test. So this is still an outstanding issue:
|
@alichaudry that PR is not merged, it may or may not pass the test you created; its not clear if this is a different issue or not. happy for you to investigate. |
@jreback So what I meant is I took the following steps:
My point is, from what I can tell my test doesn't work on the code/changes in #29131, which means those changes don't address the bug that I found. |
@alichaudry well i suspect that that PR solves some of the problem happy to take a partial or full patch |
@alichaudry pls merge master |
@alichaudry looks like CI is red - can you investigate and try to get passing? |
Hello @alichaudry! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found: There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻 Comment last updated at 2020-02-07 17:41:07 UTC |
@WillAyd At this point I'm not sure how to proceed with this PR. I know what the issue is, and I've written a test in this PR which has the correct pass/fail behavior. I also put in a hacky solution for This issue as I described it in #26564 comes from the fact that I use |
@alichaudry Will may have some more specific thoughts, but worst-case scenario you can make a PR with just the test and xfail it, so we'll know if this gets fixed down the road. |
@jbrockmendel followed your advice; updated the PR to include only the test and marked it as xfail. I am seeing some unrelated test errors (they seem to have to do with pyarrow/feather functionality) so I was wondering if you have any insight into this. I will still wait for feedback from @WillAyd. |
The pyarrow/feather failures are unrelated, you can ignore them for now. |
@WillAyd If you get a chance I'd love to hear your thoughts on this PR. It's passed all tests as expected (only failing unrelated pyarrow/feather tests). |
@@ -295,3 +296,35 @@ def test_median_duplicate_columns(): | |||
result = df.resample("5s").median() | |||
expected.columns = result.columns | |||
tm.assert_frame_equal(result, expected) | |||
|
|||
|
|||
@pytest.mark.xfail(reason="marked as xfail for: #26564") |
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.
giving a GH reference is good, but the rest of this doesnt give much information. is there a single-line description that a reader would find informative?
can you add a "GH" in front of the "#" pls
ca
The OP says that this closes #26564, is that still accurate? |
@alichaudry if you can merge master to get CI green can take another look |
closing as stale if you want to continue, please open a new PR. |
pd.groupby
seems to mutate mypd.Grouper
in-place #26564black pandas
git diff upstream/master -u -- "*.py" | flake8 --diff