-
Notifications
You must be signed in to change notification settings - Fork 927
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
cuDF error handling document #7917
Conversation
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.
Looks like a great start. Left some comments to keep the discussion moving along.
Co-authored-by: Vyas Ramasubramani <[email protected]>
Moving this PR to |
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 think we ultimately want to merge this into #11235.
I'll try and put together a POC for the exception mapping.
@isVoid that PR is merged. You should be good to go now. I might also consider merging the options page in, but that can be done in a separate PR (if you agree that it would be better that way). |
@@ -21,6 +21,7 @@ Additionally, it includes longer sections on more specific topics like testing a | |||
:maxdepth: 2 | |||
|
|||
library_design | |||
contributing_guide |
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.
@vyasr I assume you did not expose the contributing guide because it's incomplete. It should be ready to publish after we merged this PR.
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.
Yup, thanks
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.
A few minor comments, then I think we can go ahead and merge. This section is pretty minimal for now, but still important to indicate our policies around what exceptions we throw when and what level of pandas compatibility we promise. Once we have custom exception mapping I expect this section to get a little more full.
@@ -21,6 +21,7 @@ Additionally, it includes longer sections on more specific topics like testing a | |||
:maxdepth: 2 | |||
|
|||
library_design | |||
contributing_guide |
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.
Yup, thanks
Co-authored-by: Vyas Ramasubramani <[email protected]>
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.
A few minor suggestions, otherwise good!
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.
Approving assuming @bdice's comments are addressed.
Co-authored-by: Bradley Dice <[email protected]>
rerun tests |
@gpucibot merge |
This PR removes support for checking exception messages from `assert_exceptions_equal`. See #12076 for the same change made in C++, #10200 for more context, and #7917 for the change in cudf Python's developer documentation where we officially changed our policy to not consider exception payloads part of the stable API. Authors: - Vyas Ramasubramani (https://github.com/vyasr) Approvers: - Ashwin Srinath (https://github.com/shwina) URL: #12424
This document aims to give instruction the following two things: