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

Update to pandas 2 #811

Closed
1 task done
crusaderky opened this issue Apr 25, 2023 · 3 comments · Fixed by #813
Closed
1 task done

Update to pandas 2 #811

crusaderky opened this issue Apr 25, 2023 · 3 comments · Fixed by #813
Assignees

Comments

@crusaderky
Copy link
Contributor

crusaderky commented Apr 25, 2023

Blockers:

The blocker can be circumvented by doubling environments in CI, one with xarray+pandas 1.5 and another with pandas 2 and no xarray.

@mrocklin
Copy link
Member

mrocklin commented May 3, 2023

Anything still blocking this? Are we waiting for an xarray release for example? If so, what is the timeline on that?

@crusaderky
Copy link
Contributor Author

@mrocklin
Copy link
Member

mrocklin commented May 3, 2023

I wouldn't expect that to resolve any time in the immediate future, and I'd certainly like to move forward and see how Pandas 2 improvements impact benchmarks much sooner.

I'd recommend dropping Python 3.8 in benchmarks and moving on. I don't think that we need to resolve the question of when Dask drops support for Python 3.8 in order to evolve benchmarks forward.

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.

2 participants