Adds CI to run unit tests against Pandas 3.0 #220
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
ilumsden
added
area-ci
|
Also, this Action adds the |
|
I could not get PR comments working. So, instead, the CI is now going to create/update a comment in #221 based on the current state of the |
ilumsden
added
status-ready-for-review
ilumsden
force-pushed
the
pandas_3_0_testing
branch
from
7def779
to
1f522f2
Compare
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.
Pandas 3.0 is (supposedly) going to release pretty soon, and it will bring several breaking changes with it. Most notably, Pandas copy-on-write performance optimization (introduced in Pandas 1.5 and completed in Pandas 2.1) will become the default execution mode, and Pandas eager execution mode (i.e., the default since Pandas' first release) will be removed.
To help us get a head start on supporting Pandas 3.0, this PR adds a new GitHub Action that will install Thicket with Pandas 3.0 and run our unit tests. Unlike the standard CI, a failure of this new Action should not caused the overall status of the PR to be marked as a fail (i.e., the red X you see in the Pull Requests tab). It should also create and/or update a comment on the status of Pandas 3.0 support.