Consider using type.__name__ instead of str(type) in marshal_exception()

[peterzahemszky]

Consider using type.__name__ instead of str(type) in marshal_exception() for better use of that string.

In my opinion, 'ZeroDivisionError' is more useful than "<class 'ZeroDivisionError'>".

https://github.com/enthought/traits-futures/blob/main/traits_futures/exception_handling.py#L22

traits-futures/traits_futures/exception_handling.py

Lines 17 to 25 in 839a775

	def marshal_exception(e):
	"""
	Turn exception details into something that can be safely
	transmitted across thread / process boundaries.
	"""
	exc_type = str(type(e))
	exc_value = str(e)
	formatted_traceback = str(traceback.format_exc())
	return exc_type, exc_value, formatted_traceback

[mdickinson]

Thanks! I think we can squeeze a fix for this into the coming release.

See also #318, which isn't scheduled for this release.

@peterzahemszky : What do you think about using something a bit more qualified than just __name__, for example something that includes the module information? E.g., for a ZeroDivisionError we'd still get just ZeroDivisionError, but for something like TraitError we'd get traits.trait_errors.TraitError?

[mdickinson]

So we probably want something that uses both __module__ and __qualname__, except in the case where the module is builtins. This is close to what CPython does to construct the repr of a class: https://github.com/python/cpython/blob/2f180ce2cb6e6a7e3c517495e0f4873d6aaf5f2f/Objects/typeobject.c#L1076-L1092

[mdickinson]

@peterzahemszky See #391 for a possible fix; feedback on whether this fits your use-case would be welcome.