RetroSearch Browse

Fri Mar 11 13:23:48 CET 2005 · https://mail.python.org/pipermail/python-dev/2005-March/052037.html

Peter Astrand wrote:

>On Fri, 11 Mar 2005, Paul Moore wrote:
>
>  
>
>>>Not sure this is pertinent but anyway: "any" and "all" are often used
>>>as variable names. "all" especially often and then almost always as a
>>>list of something. It would not be good to add "all" to the list of
>>>words to watch out for. Also, "all" is usually thought of as a list of
>>>      
>>>
>
>  
>
>>Using "any" and "all" as variables hides the builtins, but doesn't
>>disallow their use elsewhere. Personally, though, I wouldn't use "any"
>>or "all" as variable names, so that's a style issue.
>>    
>>
>
>Even though you can use them as variables (and shadow the builtins), you
>will still get warnings from "pychecker". The code will also be harder to
>read: When you see "all" in the middle of some code, you don't know if
>it's referring to the builtin or a variable.
>
>Personally, I think Python has too many builtins already.
>
>  
>
to extend the naming pool, FWIW CL calls similar things EVERY and SOME.

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

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

[Python-Dev] Adding any() and all()