This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author orsenthil
Recipients Douglas.Leeder, belopolsky, docs@python, max, orsenthil, rhettinger, stutzbach
Date 2010-10-10.03:49:44
SpamBayes Score 4.329596e-06
Marked as misclassified No
Message-id <20101010034935.GA3487@remy>
In-reply-to <AANLkTikO4pugmpBuZR=n7NBfMn5fHWPd_d7yh4GDFXQ1@mail.gmail.com>
Content
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.
History
Date User Action Args
2010-10-10 03:49:46orsenthilsetrecipients: + orsenthil, rhettinger, belopolsky, stutzbach, docs@python, Douglas.Leeder, max
2010-10-10 03:49:45orsenthillinkissue10029 messages
2010-10-10 03:49:44orsenthilcreate