Skip to content

Conversation

@leouieda
Copy link
Member

Pandas was issuing FutureWarnings about calling Series.ravel, which could be fixed by calling np.ravel() instead, and a keyword argument of the groupby .apply changing the default to not include the index in the calculations (which is the right thing to do).

Pandas was issuing FutureWarnings about calling `Series.ravel`, which
could be fixed by calling `np.ravel()` instead, and a keyword argument
of the groupby `.apply` changing the default to not include the index in
the calculations (which is the right thing to do).
@leouieda
Copy link
Member Author

@santisoler the other warning about aggregate I couldn't find a way to fix. I think we'll just have to live with it until Pandas makes a new release. Or we pass strings to BlockReduce instead of functions but I'm not a huge fan.

@leouieda
Copy link
Member Author

So the pandas warning about apply won't work on older pandas...

I think we should leave it as is and let pandas change their default when they want. It's not like we're doing something completely wrong since the tests pass with or without the new argument.,

@leouieda leouieda changed the title Fix pandas warnings about .ravel() and .apply() Fix pandas warnings about .ravel() Apr 17, 2024
@leouieda leouieda merged commit fcd5b24 into main May 28, 2024
@leouieda leouieda deleted the pandas-warnings branch May 28, 2024 13:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants