Skip to content
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

[compat]: Fixed test for pandas>2 #251

Merged
merged 5 commits into from
Apr 25, 2023

Conversation

TomAugspurger
Copy link
Contributor

pandas 2.0 changed a behavior w.r.t. groupby and non-numeric columns. This test doesn't need to drop the columns anymore. xref geopandas/geopandas#1999

pandas 2.0 changed a behavior w.r.t. groupby and non-numeric columns.
This test doesn't need to drop the columns anymore.
xref geopandas/geopandas#1999
@TomAugspurger
Copy link
Contributor Author

The failures in https://github.com/geopandas/dask-geopandas/actions/runs/4778643792/jobs/8495193757?pr=251 are fixed by #242 (confirmed by cherry picking and running locally)

Several of the other tests failed because of a pin on dask, but not pandas. Older versions of dask are not compatible with pandas>=2.0. I've pinned pandas in the 38-minimal environment and unpinned dask elsewhere. So we should just see the parquet failures.

@TomAugspurger
Copy link
Contributor Author

@jorisvandenbossche I'd recommend merging #242 first, which should be good to go, and then I'll update this to confirm that CI is passing.

Copy link
Member

@martinfleis martinfleis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

I suppose we should cut a patch release after this...

@martinfleis martinfleis merged commit dfedd59 into geopandas:main Apr 25, 2023
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