-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
String dtype: avoid surfacing pyarrow exception in binary operations #59610
Merged
WillAyd
merged 12 commits into
pandas-dev:main
from
jorisvandenbossche:string-dtype-operations-error
Aug 27, 2024
Merged
Changes from 1 commit
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
ae69206
String dtype: avoid surfacing pyarrow excetion in binary operations
jorisvandenbossche ff1f57e
fix expected exception in test_arrow.py
jorisvandenbossche 227b42a
fix test_sub_fail for infer_string
jorisvandenbossche 2426cc5
fix expected exception in test_string.py
jorisvandenbossche 34a970a
try fix type annotations
jorisvandenbossche 649dad1
try fix type annotations
jorisvandenbossche 946abca
fix failures
jorisvandenbossche ea4163d
clean-up more tests
jorisvandenbossche 2e9b0d1
try fixing type annotations
jorisvandenbossche 44c0090
try fixing type annotations
jorisvandenbossche cda40ee
Merge remote-tracking branch 'upstream/main' into string-dtype-operat…
jorisvandenbossche 843671c
fixup
jorisvandenbossche File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am doing
from err
here, so the original pyarrow message like "ArrowNotImplementedError: Function 'binary_join_element_wise' has no kernel matching input types (large_string, int64, large_string)" is still visible up in the traceback.For the new string dtype, I would actually be fine with suppressing this (using
from None
) to limit the length of the error traceback. But for usage of ArrowDtype in general, I suppose this information is still very useful to see.But as I mentioned in the top post, I could also only do this try/except in case we are in ArrowStringArray, and leave the generic ArrowExtensionArray as is (raising the pyarrow error directly)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the
from err
- I don't see a huge harm in including all of that information