Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #37105

Re: PyWart: Exception error paths far too verbose

Show all headers | View raw

On Wednesday, 16 January 2013 15:23:55 UTC+5:30, Terry Reedy  wrote:
> On 1/16/2013 12:59 AM, Rick Johnson wrote:
> 
> >
> 
> > Python needs to trim the path to the source file from which the
> 
> > exception was caught and only display the relative path starting from
> 
> > your personal library folder.
> 
> >
> 
> > For example. Say your personal library exists in:
> 
> >
> 
> > C:\users\user\documents\python\lib
> 
> >
> 
> > ...then there is no need to post THAT portion of the path EVERY
> 
> > STINKING TIME! For instance, let's say a script at:
> 
> >
> 
> > C:\users\user\documents\python\lib\sound\effects\echo.py
> 
> >
> 
> > ...throws an error. What will we see?
> 
> >
> 
> > Traceback (most recent call last): File
> 
> > "C:\users\user\documents\python\lib\sound\effects\echo.py", line N,
> 
> > in BLAH
> 
> >
> 
> > Why do i need to see "C:\users\user\documents\python\lib" EVERY
> 
> > time?
> 
> >
> 
> > Since all directories *BELOW* the directory that holds your personal
> 
> > Python library are /superfluous/ when posting exceptions to stderr,
> 
> > trimming this bloat can really help to make exception messages easier
> 
> > to read.
> 
> >
> 
> > Traceback (most recent call last): File
> 
> > "...\sound\effects\reverb.py", line XXX, in YYY
> 
> 
> 
> 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.
> 
> 
> 
> Are you are aware of
> 
> '''
> 
> sys.excepthook(type, value, traceback)
> 
> 
> 
>      This function prints out a given traceback and exception to sys.stderr.
> 
> 
> 
>      When an exception is raised and uncaught, the interpreter calls 
> 
> sys.excepthook with three arguments, the exception class, exception 
> 
> instance, and a traceback object. In an interactive session this happens 
> 
> just before control is returned to the prompt; in a Python program this 
> 
> happens just before the program exits. The handling of such top-level 
> 
> exceptions can be customized by assigning another three-argument 
> 
> function to sys.excepthook.
> 
> '''
> 
> This is how some apps and environments customize exception reporting 
> 
> (and logging). I believe some people also put a replacement in their 
> 
> site module.
> 
> 
> 
>  >>> import sys; sys.excepthook
> 
> <built-in function excepthook>
> 
> 
> 
> I expect the default, excepthook, is something like
> 
> 
> 
> def excepthook(typ, value, traceback):
> 
>      print('Traceback (most recent call last):', file=sys.stderr)
> 
>      for item in traceback:
> 
>          print(format_tb_item(item), file=sys.stderr)
> 
>      print('{}: {}'.format(typ.__name__, value), file=sys.stderr)
> 
> 
> 
> (or the equivalent with sys.stderr.write)
> 
> 
> 
> 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.
> 
> 
> 
> 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!)
> 
> 
> 
> -- 
> 
> Terry Jan Reedy

Right-click the file in the traceback and there is an "Go to file/line" option.

Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

PyWart: Exception error paths far too verbose Rick Johnson <rantingrickjohnson@gmail.com> - 2013-01-15 21:59 -0800
  PyWart: Exception error paths far too verbose donarb <donarb@nwlink.com> - 2013-01-16 00:31 -0800
    Re: PyWart: Exception error paths far too verbose Chris Angelico <rosuav@gmail.com> - 2013-01-16 19:39 +1100
  Re: PyWart: Exception error paths far too verbose Terry Reedy <tjreedy@udel.edu> - 2013-01-16 04:53 -0500
    Re: PyWart: Exception error paths far too verbose Rick Johnson <rantingrickjohnson@gmail.com> - 2013-01-16 08:43 -0800
      Re: PyWart: Exception error paths far too verbose Terry Reedy <tjreedy@udel.edu> - 2013-01-16 19:51 -0500
        Re: PyWart: Exception error paths far too verbose Rick Johnson <rantingrickjohnson@gmail.com> - 2013-01-18 16:34 -0800
        Re: PyWart: Exception error paths far too verbose Rick Johnson <rantingrickjohnson@gmail.com> - 2013-01-18 16:34 -0800
    Re: PyWart: Exception error paths far too verbose Rick Johnson <rantingrickjohnson@gmail.com> - 2013-01-16 08:43 -0800
    Re: PyWart: Exception error paths far too verbose Ramchandra Apte <maniandram01@gmail.com> - 2013-01-19 19:15 -0800
      Re: PyWart: Exception error paths far too verbose Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-01-20 06:08 +0000
        Re: PyWart: Exception error paths far too verbose Terry Reedy <tjreedy@udel.edu> - 2013-01-20 11:08 -0500
  Re: PyWart: Exception error paths far too verbose Michael Torrie <torriem@gmail.com> - 2013-01-16 07:20 -0700
    Re: PyWart: Exception error paths far too verbose Rick Johnson <rantingrickjohnson@gmail.com> - 2013-01-16 08:31 -0800
    Re: PyWart: Exception error paths far too verbose Rick Johnson <rantingrickjohnson@gmail.com> - 2013-01-16 08:31 -0800
  Re: PyWart: Exception error paths far too verbose Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-01-16 14:45 +0000
    Re: PyWart: Exception error paths far too verbose Rick Johnson <rantingrickjohnson@gmail.com> - 2013-01-16 09:32 -0800
      Re: PyWart: Exception error paths far too verbose Chris Angelico <rosuav@gmail.com> - 2013-01-17 08:21 +1100
      Re: PyWart: Exception error paths far too verbose alex23 <wuwei23@gmail.com> - 2013-01-16 16:33 -0800

csiph-web