-
Notifications
You must be signed in to change notification settings - Fork 48
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
Dataset: fix bug revealed by pandas 1.0 #561
Conversation
Can we bump minimum versions? |
Of pandas? This PR should work with pre-1.0 pandas just fine. |
@dgasmith Any idea what might be going on here:
|
@mattwelborn Yea, sparse molecule bug. @doaa-altarawy What do you think of the fix? |
@dgasmith @doaa-altarawy I think we're back to database bugs now. |
b3d1877
to
cbdaf7e
Compare
@mattwelborn Can you reproduce the single failure? I cannot seem to manage it locally. |
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.
Merging, this moves the bar forward. I will see if I can track down the remaining error.
Description
CI is failing. This seems to be caused by
df = df.groupby(["name"])["return_result"].sum(skipna=True)
. It appears thatskipna
was never a valid kwarg ofgroupby().sum()
, but that it was not checked until pandas 1.0. This PR removesskipna=True
; the default behavior is to skip NaNs already.Changelog description
Fixed a bug that caused errors with pandas v1.0.
Status