{{ message }}
Fix exception chaining for non-built-in exceptions#9266
Merged
Conversation
Collaborator
|
@justmobilize so are you saying it works for you? Not sure :) |
dhalbert
approved these changes
May 21, 2024
dhalbert
left a comment
dhalbert
left a comment
Collaborator
There was a problem hiding this comment.
Thank you for the quick fix!
Merged
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The cause was that setting the
__cause__property on an exception didn't set the built in exception object's cause property, so it's necessary to fetch the property from the actual object when needed.