[Python-Dev] Rationale for sum()'s design? (original) (raw)
Guido van Rossum gvanrossum at gmail.com
Mon Mar 14 18:36:23 CET 2005
- Previous message: [Python-Dev] Rationale for sum()'s design?
- Next message: [Python-Dev] Rationale for sum()'s design?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, 15 Mar 2005 00:05:32 +1000, Nick Coghlan <ncoghlan at iinet.net.au> wrote: [...]
Maybe what we really should be doing is trapping the TypeError, and generating a more meaningful error message.
E.g. [...] ... try: ... value += first ... except TypeError: ... raise TypeError("Cannot add first element %r to initial value %r" % (first, value))
No, no, no! NO! Never catch a general exception like that and replace it with one of your own. That can cause hours of debugging pain later on when the type error is deep down in the bowels of the += operation (or perhaps deep down inside something it invoked).
-- --Guido van Rossum (home page: http://www.python.org/~guido/)
- Previous message: [Python-Dev] Rationale for sum()'s design?
- Next message: [Python-Dev] Rationale for sum()'s design?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]