-
Notifications
You must be signed in to change notification settings - Fork 51
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
Pin pandas>=2.2 #413
Comments
@jaclark5 Do you think it is possible to make the current code work with both pandas 2.2 and 2.1? |
This error is likely because the columns for single lambda simulations are not tuples when calling It seems to me that the solution would be to have all lambda state column headers be tuples all the time. That would take a bit of reformatting. |
@jaclark5 I do agree that ave all lambda state column headers be tuples all the time would be good but that might break a lot of people's implementation as in most cases lambda would be a single float. |
@xiki-tempula @orbeckst I looked at the changes to
This warning is quite annoying since as soon as you given it the tuple it requests, it undoes that... it seems like heeding this warning was premature as pandas has not yet transitioned to the internal handling of groups that they envision and are seemingly laying the ground work for. It seems my PR should be removed to allow alchemlyb to function with the greatest breadth of pandas versions and it can be reintroduced or adjusted in the future when I no longer think adjusting alchemlyb to use tuples in lambda state columns will resolve the issue, since the output of |
#407 won't work with pandas<2.2
Gives
For workflow.
The text was updated successfully, but these errors were encountered: