refactor(rust): Map Polars AssertionError
to pyo3's AssertionError
and improve macro flexibility
#21495
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 PR is regarding comments from @coastalwhite on this PR: #21460 and from Discord regarding using pyo3's built in
AssertionError
and using the macro for more general assertions.Previous PR relates to issue: #21388.
polars-error/lib.rs
, the macro has been updated to be more generalize and also match the already existing Python assertion error.error.rs
,PolarsError::AssertionError
has been mapped toPyAssertionError
rather than making a new exception.exceptions.rs
, thecreate_exception_macro!()
has been removed forAssertionError
since it will be relying on pyo3's existing implementation.