Ability to convert exceptions into strings #4178
Comments
10 tasks
|
if you don't need traceback, exc can be converted to PyObjectRef and PyObject has for exc: PyBaseExceptionRef, |
|
Why can't the traceback work without calling vm.print_exception? |
|
The messages are definitely better now, had to do this to just get a string: let err_string: String = err.to_pyobject(vm).repr(vm).unwrap().to_string(); |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've been working in a strict wasm32-unknown-unknown environment, and I've been having a hard time with exceptions from the vm, as when you print them the string is not very useful at all. I just found
vm.print_exceptionand it has actually useful information in it. This method works great ifprintlnworks in you environment, but in the wasm32-unknown-unknown environment I'm in I can't use theprintlnmacro directly. It would be great if the RustPython errors had a method called something liketo_readable_stringor something that will do the same thing asvm.print_exception, but instead return the error so that it can be dealt with in other ways.The text was updated successfully, but these errors were encountered: