RetroSearch Browse

Tue Oct 25 22:35:14 CEST 2005 · https://mail.python.org/pipermail/python-dev/2005-October/057636.html

[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.

--
--Guido van Rossum (home page: http://www.python.org/~guido/)

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

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

[Python-Dev] Proposed resolutions for open PEP 343 issues