refactor: Connect Python assert_series_equal()
to Rust back-end
#23141
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.
@coastalwhite
This is the first PR to connect the the new Rust back-end testing functionality to Python. This PR only covers
assert_series_equal()
since I didn't want the PR to be too large and it was my first time doing something like this. The next PR will coverassert_dataframe_equal()
.I didn't want to meddle too much in the existing Python tests since they are robust and well-written, so I only made 2 very minor changes to the tests because of how they were structured. Otherwise, all tests pass without any interference.
Lastly, the now deprecated Python code has still not been removed from the related files. This is because the Python
assert_dataframe_equal()
functionality in Python still relies on that code, so if I delete it without first connecting it to the Rust back-end, it causes a lot of issues. The code will be removed during the PR for connectingassert_dataframe_equal()
.