Skip to content

Resolve multiple warnings with latest pandas version (2.2.0) #680

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

Closed
desilinguist opened this issue Feb 2, 2024 · 2 comments · Fixed by #684
Closed

Resolve multiple warnings with latest pandas version (2.2.0) #680

desilinguist opened this issue Feb 2, 2024 · 2 comments · Fixed by #684
Assignees

Comments

@desilinguist
Copy link
Member

desilinguist commented Feb 2, 2024

Seeing the following warnings in the report:

Pyarrow will become a required dependency of pandas in the next major release of pandas (pandas 3.0),
(to allow more performant data types, such as the Arrow string type, and better interoperability with other libraries)
but was not found to be installed on your system.
If this would cause problems for you,
please provide us feedback at https://github.com/pandas-dev/pandas/issues/54466
        
  import pandas as pd
When grouping with a length-1 list-like, you will need to pass a length-1 tuple to get_group in a future version of pandas. Pass `(name,)` instead of `name` to silence this warning.
SeriesGroupBy.grouper is deprecated and will be removed in a future version of pandas.
@desilinguist desilinguist self-assigned this Feb 2, 2024
@desilinguist
Copy link
Member Author

Turns out some of the warnings in the report were a result of how seaborn was using pandas and they have been fixed in the latest version of seaborn=0.13.2. @mulhod since you were seeing these warnings in the wild, can you confirm the upgrading seaborn removes all of them except the pyarrow one?

@desilinguist
Copy link
Member Author

desilinguist commented Feb 20, 2024

There are two additional warnings showing up when running the tests:

The behavior of DataFrame concatenation with empty or all-NA entries is deprecated. In a future version, this will no longer exclude empty or all-NA columns when determining the result dtypes. To retain the old behavior, exclude the relevant entries before the concat operation.

and

Downcasting behavior in Series and DataFrame methods 'where', 'mask', and 'clip' is deprecated. In a future version this will not infer object dtypes or cast all-round floats to integers. Instead call result.infer_objects(copy=False) for object inference, or cast round floats explicitly. To opt-in to the future behavior, set `pd.set_option('future.no_silent_downcasting', True)

Out of these, there second is a spurious warning that will be fixed in the upcoming v2.2.1 release of pandas.

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 a pull request may close this issue.

1 participant