On Fri, Oct 08, 2010 at 06:25:26PM +0000, Alexander Belopolsky wrote: > In this case, I wonder if "equivalent to" code should be added to the > section for enumerate() and map(). Also since any() and all() have > "equivalent to" code, I think min(), max() and sum() deserve it as > well.
I think, you are asking for consistency in docs, right? As a sidenote those explanations should be okay, but merging it with the explanation of the functions may add to confusion (like the zip example did in this case). Even I am +1 on removing that complex equivalent code in the zip documentation, as it can confusing to the newcomer. But I am also okay with moving that 'equivalent to code' further down in the explanation. _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
