Update dependencies to Pandas v2.0 #1112
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
matt-graham
changed the title
matt-graham
force-pushed
the
mmg/update-dependencies-pip
branch
2 times, most recently
from
efa9133 to
fc43ba8
Compare
matt-graham
force-pushed
the
mmg/update-dependencies-pip
branch
from
fc43ba8 to
829e6cf
Compare
|
Tests now all passing with #1142 merged 🎉 |
tamuri
approved these changes
Sep 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Stop-gap solution as part of #763 which just updates existing
pipbased requirement files rather than also switching to fullycondabased approach as in #949.Given Pandas v2.1 has now been released assuming it is probably worth updating to use this assuming there aren't any major additional breaking changes over switch to v2.0 (which it doesn't look like there is from release notes).Edit: Pandas v2.1 only support Python 3.9+ so rolling back pin to Panda v2.0 to maintain Python 3.8 compatibility for now.
From running tests locally it looks like at least some tests fail due to changes which are not Panda v2.0 compatible since I last worked on this, so will need to find and fix all of these first so marking this as draft for now.