(original) (raw)
On Wed, Nov 5, 2014 at 2:47 PM, R. David Murray <rdmurray@bitdance.com> wrote:
As I said on the issue, there is no reason I can see to add extra code
just to turn an AttributeError into a TypeError. The AttributeError
works just fine in letting you know your input type didn't work.
+1
Unlike ValueError or LookupError, TypeError and AttributeError indicate a logical problem with the code rather than an issue with the user input. From the programmer perspective, any code that catches and mutates exceptions is a nuisance.