RetroSearch Browse

Thu Sep 30 21:37:17 CEST 2004 · https://mail.python.org/pipermail/python-dev/2004-September/049151.html

At 12:52 PM 9/30/04 -0300, Lalo Martins wrote:
>On Thu, Sep 30, 2004 at 10:19:22AM -0400, Phillip J. Eby wrote:
> >
> > Also, maybe in 2.5 we could begin warning about bare excepts that aren't
> > preceded by non-bare exceptions.
>
>try:
>   foo()
>except:
>   print_or_log_exception_in_a_way_that_is_meaningful()
>   raise
>
>doesn't seem to be incorrect to me.  For example, if the program
>is a daemon, I want the exception logged somewhere so that I can
>see it later, because I won't be watching stderr.

1. If the exception raised is a MemoryError, your daemon is in trouble.

2. I said *warn*, and it'd be easy to suppress the warning using 'except 
Exception:', if that's what you really mean

3. But I suppose this could be considered a job for pychecker.

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2004-September/049151.html below:

[Python-Dev] Proposing a sys.special_exceptions tuple