PyWart: Exception error paths far too verbose

[Rick Johnson]

On Wednesday, January 16, 2013 3:53:55 AM UTC-6, Terry Reedy wrote:

> I agree with the complaint and you may have the germ of a good idea. The 
> problem is that for some tracebacks, paths jump all over the place 
> rather than having a common prefix. Dealing with this might require 
> preprocessing the entire traceback before iterating and printing each item.

Your comment is too ambiguous for me to comprehend... Are you referring to the case where devs keep python modules and scripts in /many/ places on their disc, or something else?

> Are you are aware of
> '''
> sys.excepthook(type, value, traceback)
> 
>      This function prints out a given traceback and exception to sys.stderr.
> 
> [...]
>
> This is how some apps and environments customize exception reporting 
> (and logging). I believe some people also put a replacement in their 
> site module.


I'll check it out. If the path can be trimmed there, then the problem is solved for me, but what about everyone else?

> What you want to change is format_tb_item (possibly, as I said, after 
> scanning traceback before the print loop). If you come up with something 
> nice, I would like to see it.

If i do i will post it. First i need to respond to someone who always needs me to explain every detail because he has trouble comprehending even the simplest of ideas. *cough*even*cough*prano

> The only thing special that IDLE does now is to color the text red. I 
> should sometime see how that is done. (Being able to doubleclick on an 
> item and have IDLE open an edit window at the specified line would be 
> really nice!)

IDLE already has a build in command from the context menu called "go to file/line" that will parse any right-clicked line for file paths and line numbers, then, open that file in a new IDLE editor instance and adjust the view so you can see the lineno in question (typical IDE stuff)... but most devs prefer to use IDEs with less bugs asinine interfaces :-)