Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #36894
| Date | 2013-01-16 07:20 -0700 |
|---|---|
| From | Michael Torrie <torriem@gmail.com> |
| Subject | Re: PyWart: Exception error paths far too verbose |
| References | <e887a93f-ea32-442c-9673-4da892b9f37e@googlegroups.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.569.1358346026.2939.python-list@python.org> (permalink) |
On 01/15/2013 10:59 PM, Rick Johnson wrote: > Why do i need to see "C:\users\user\documents\python\lib" EVERY time? You're thinking about things from a very windows-centric point of view. There are many cases where as a developer I need to see the full paths. My modules are not always going to be in a common subfolder. Django apps, for example, live in an arbitrary folder, in my case, /var/www/apps on my web server. Sometimes they live in my home projects folder. Django itself lives partly in /usr/lib/python2.7/site-packages and partly in /usr/share/django. Granted most of my errors are going to happen in my own code, which is in /var/www/apps/blah. But occasionally I might uncover a django bug (less likely of course). Seeing the full path is essential for me. As well, runtime errors get logged as the system is serving, and they could come from any of my apps, depending on how bad a programmer I am. Finally, in an ideal world, all runtime errors should be trapped by the program. The end user should never see them. Sure in my django apps things go south from time to time. But typically the trace gets logged to a file, and the end user sees a 503 error, and gives me a call. Ideally of course, the code should recover gracefully and let the user do most of what he wants. Traces are for developers, not users.
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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