Am I the only one who finds Python's "forwards" backtraces confusing compared to every other language I've used? I can't help but think at least part of this confusion is because of that.

That said:

* Would printing the trace as a tree actually clarify anything?

* Good code almost always minimizes the amount of code in an exception handler.

* `raise_exception()` is generally bad practice; consider `raise get_exception()` if you need something complicated (among others, this allows choice of `from`)

* `raise ... from None` is useful since it's often the most recent stacktrace that's actually relevant.

* `raise ... from e` likely implies that it is the older stacktrace that's most relevant; ideally this would just be a single annotation on a particular frame "exception was replaced here".