Travis A. Everett added the comment:
Thanks, Martin--I should've thought to check to see if it'd just been pushed
back in the list. I was just focusing on a workaround for another problem and
did a double-take when the traceback value didn't match what was set.
This resolution is fine by me
New submission from Travis A. Everett:
When BaseException.with_traceback(tb) is used, the __traceback__ property is
properly set, but the property gets overwritten when the exception is raised.
The attached file demonstrates the issue by raising exception a, which doesn't
use with_traceback
