CI Pin pandas<2.2 to avoid DeprecationWarning #28273
Closed
Conversation
This file contains hidden or 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
|
Pandas 2.2 has introduced a lot of new deprecation warnings though. We don't do much pandas, but I think it would be nice to not pin and make sure we fix any issues if we find them. |
|
Yeah agreed, I am just thinking as the quickest way to do this to unlock other things ... There seems to be genuine CI errors for now anyway to deal with. Things are never as simple as they should be 😢 |
|
Closing this one, since we will need anyway to tackle the warnings in the scipy-dev build ... |
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.
This seems the simplest thing to do until the dust settles down in pandas-dev/pandas#54466.
The alternative is to ignore warnings or install Pyarrow, for example #28258.
Closes #28216
For now I have updated only the main CI build. There is currently an issue with scipy-dev that times out more often than previously (maybe scipy 1.12 not sure) see PR that was opened by scikit-learn-bot