Skip to content
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

Issue 96 improved exception handling #115

Merged
merged 2 commits into from
Mar 12, 2015

Conversation

Lenbok
Copy link
Contributor

@Lenbok Lenbok commented May 18, 2014

I initially applied just the patch that is described in #96, but then wanted to go further -- primarily so that on the python side I can distinguish between exception types and decide whether to locally handle the exception or whether to propagate the exception up (perhaps with exception rewrapping).

Lenbok and others added 2 commits May 16, 2014 12:12
- Disable calling ExceptionDescribe, as this pollutes stderr, making it harder
to implement clean exception handling. JNI documentation describes it as being for
debugging purposes.

- Extract separate fields for the exception class name, exception message, and
exception stack trace, and add these as attributes to JavaException. Calling
code can now decide for itself whether and how to present this information.
tito added a commit that referenced this pull request Mar 12, 2015
@tito tito merged commit 9425a2c into kivy:master Mar 12, 2015
@tito
Copy link
Member

tito commented Mar 12, 2015

I didn't saw this PR, someone just pointed it in the mailing list. Great job!!

@Lenbok Lenbok deleted the issue-96-exception-handling branch January 31, 2019 19:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants