[Python-Dev] containment checking

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

On 20/03/2010 00:19, Glenn Linderman wrote:
> On 3/19/2010 5:18 PM, Michael Foord wrote:
>>>>> 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.
>> Michael 
> Who, me?  The containment checking code would contain the try/except, 
> I was proposing.

Explicit by the programmer. That is what explicit means... Caught and 
silenced for you by Python is implicit.


> Glenn


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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20100320/59527487/attachment.html>

More information about the Python-Dev mailing list