Closed MHDante closed 1 year ago
Perhaps this introduces a breaking change for those who were expecting to catch a RuntimeError in the initialization. This could be addressed by hiding this behind a VERBOSE flag or by inspecting the exception itself. Both of these are a bit more difficult, and I won't have time to properly add them to the library
That's not really the proper way to deal with this. Just letting the exception "rip through" will likely break both Mono and Python on the way. A proper solution would need to actually interpret the information from the raised exceptions.
I'll close this. We can't merge it in the current shape.
Removed a dummy exception that gets passed into the initializer.
This allows proper information to be printed when the function call fails.
Before:
After
Changing this allowed me to notice that my
libmono-native.dylib
file was misplaced.It seems likely that being verbose in this scenario is preferable.