[Python-Dev] containment checking

Michael Foord fuzzyman at voidspace.org.uk
Sat Mar 20 01:18:09 CET 2010

On 20/03/2010 00:15, Glenn Linderman wrote:
> On 3/19/2010 4:58 PM, Antoine Pitrou wrote:
>> Glenn Linderman<v+python<at> g.nevcal.com> writes:
>>> > > If there's a bug in your __eq__ method, it may or may not raise an
>>> > exception, which may or may not get you wrong containment results. 
>>> But
>>> > it will probably get you buggy results, somehow or another. That's 
>>> what
>>> > design, code reviews, and testing are for.
>> We'll have to "agree to disagree" then. If you want error silencing 
>> by default,
>> Python is not the language you are looking for.
> We can agree to disagree, if you like. But taken to the limit, the Zen 
> you quoted would prevent the try except clause from being used.

No, that is what "unless explicitly silenced" means - you are proposing 
to silence them *without* an explicit try except clause.


> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> http://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: 
> http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk 


READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.

More information about the Python-Dev mailing list