RetroSearch Browse

Fri Aug 5 10:12:25 CEST 2005 · https://mail.python.org/pipermail/python-dev/2005-August/055156.html

James Y Knight <foom at fuhm.net> wrote: 

> > OK, I'm changing my mind again about the names again.
> >
> > Exception as the root and StandardError can stay; the only new
> > proposal would then be to make bare 'except:' call StandardError.
> 
> I don't see how that can work. Any solution that is expected to  
> result in a usable hierarchy this century must preserve "Exception"  
> as the object that user exceptions should derive from (and therefore  
> that users should generally catch, as well). There is way too much  
> momentum behind that to change it.

Well, in the last few years I always derived my own exceptions from
StandardError and used `except StandardError` instead of `except
Exception`.

And I'd love to get rid of the

    except KeyboardInterrupt:
        raise

clause I currently have to write before any `except
StandardError`. 
-- 
Christian Tanzer                                    http://www.c-tanzer.at/

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

Showing content from https://mail.python.org/pipermail/python-dev/2005-August/055156.html below:

Exception Reorganization for Python 3.0