Draft
Conversation
Member
|
@Thrameos Since it came up lately (line no = -1 vs line no = 0), is this PR obsolete? |
Contributor
Author
|
Likely though I don't remember what this was for. I think I was trying at one point to unify the exception outputs more closely. But was lost along the why fighting the lack of Python support for exceptions. |
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
2 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.
This is a work in progress to link Java exception causes with Python ones. Unfortunately, the cause slot is already used when throwing from Java to Python, so it is not clear if this can actually be made into a function PR.
Potentially fixes #1047