-
Notifications
You must be signed in to change notification settings - Fork 747
Populate .NET's InnerException from exc.__cause__ when available #893
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
Comments
lostmsu
added a commit
to losttech/pythonnet
that referenced
this issue
Jun 24, 2019
This change only affects some exception handling, but not all of it. Instead, parameterless PythonException constructor is made Obsolete. PythonException.FromPyErr() should be called instead. FromPyErr will check __cause__, and, if present, parse it into InnerException property. This change will cause a slowdown, as I found no way to read __cause__ on demand, because InnerException is not virtual. This addresses pythonnet#893
lostmsu
added a commit
to losttech/pythonnet
that referenced
this issue
Jun 25, 2019
lostmsu
added a commit
to losttech/pythonnet
that referenced
this issue
Jun 25, 2019
PythonException.FromPyErr was not properly handling __cause__ of None
Makes sense |
4 tasks
lostmsu
added a commit
to losttech/pythonnet
that referenced
this issue
May 6, 2020
lostmsu
added a commit
to losttech/pythonnet
that referenced
this issue
May 13, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
PythonException
objects should provideInnerException
property when__cause__
is set in the original Python exception. This is a reverse-direction of feature #223The text was updated successfully, but these errors were encountered: