Guido van Rossum wrote: > [Eric "are all your pets called Eric?" Nieuwland] >>>> Hmmm... Would it be reasonable to introduce a ProtocolError >>>> exception? > > [Guido] >>> And which perceived problem would that solve? > > [Eric] >> It was meant to be a bit more informative about what is wrong. >> >> ProtocolError: lacks __enter__ or __exit__ > > That's exactly what I'm trying to avoid. :) > > I find "AttributeError: __exit__" just as informative. In either case, > if you know what __exit__ means, you'll know what you did wrong. And > if you don't know what it means, you'll have to look it up anyway. And > searching for ProtocolError doesn't do you any good -- you'll have to > learn about what __exit__ is and where it is required.
I see. Then why don't we unify *Error into Error? Just read the message and know what it means. And we could then drop the burden of exception classes and only use the message. A sense of deja-vu comes over me somehow ;-) _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
