@willmcgugan Honest truth - While I apreciate the engineering effort that goes into this kind of feature, and I appreciate that I'm just one opinion - I'd very much like tools to *stop "fixing" tracebacks*. My biggest complaint about both Rich and Pytest as tools is the way they "enhance" stack traces. I *have* the code sitting *right here*. I can *find* the context around "line 130". I don't need my console filled with all the context of line 130, and all the context calling line 130, etc

@willmcgugan These kinds of improvements turn a 5 line stack trace into a 5 page epic poem, making it a lot harder (for me) to interpret the context of an error; and if the "enhanced" error finds its way into a log - good luck with that, because the log is now unreadable. The presentation has been so strongly customized for a specific screen width that it's a nightmare to interpret.

I don't expect anything to change... but no, Sir, I don't like it :-)