Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #37038
| Newsgroups | comp.lang.python |
|---|---|
| Date | 2013-01-18 16:34 -0800 |
| References | <e887a93f-ea32-442c-9673-4da892b9f37e@googlegroups.com> <mailman.565.1358330072.2939.python-list@python.org> <85ec4ecd-4d28-4c3e-980f-d7668e059eed@googlegroups.com> <mailman.585.1358383925.2939.python-list@python.org> |
| Subject | Re: PyWart: Exception error paths far too verbose |
| From | Rick Johnson <rantingrickjohnson@gmail.com> |
| Message-ID | <mailman.657.1358555706.2939.python-list@python.org> (permalink) |
On Wednesday, January 16, 2013 6:51:31 PM UTC-6, Terry Reedy wrote: > I missed in your original post that you only want one consistent > personal library path abbreviated, leaving everything else alone. So the > above is not applicable. And a custom excepthook very easy. > > How should the traceback mechanism -will- know what that path is? Well, the jury is still deliberating on the specifics, however, as for myself, i would sway more to the /explicit/ side. A few possibilities include: * A configuration file. Python already checks the current directory for ".pth" files, which it then reads and adds the contained paths to sys.path -- most folks stopped typing commands OVER and OVER on the commandline many years ago. But to each his own. * A runtime command or keyword placed in a script (YUCK!) * A commandline switch (only good for members of the python historical society.)
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