> >>>>>> "JA" == James Althoff <James_Althoff@i2.com> writes:
> >
> > JA> would it make sense to make AttributeError a subclass of
> > JA> TypeError so that
> >
> > JA> except (TypeError):
> >
> > JA> would become equally "safe" (and simpler)?
>
> [Barry]
>
> >No, but it /might/ make sense to give them a new common base class
> >between them and Exception. If so, called what?
>
> ProtocolException.
>
> I think it would have made sense, but it probably wouldn't have helped.
> Users still see a specific exception thrown and write code against that.
Yeah, the problem with Jim's proposal is that users who write
try:
"try something"
except TypeError:
"one way of handling it"
except AttributeError:
"another way of handling it"
will still see a change in behavior, as will users who catch
only AttributeError in a situation that now raises TypeError...
--Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4