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 rhettinger
Recipients docs@python, georg.brandl, rhettinger, serhiy.storchaka, terry.reedy
Date 2014-12-15.02:26:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1418610395.24.0.967138011118.issue23049@psf.upfronthosting.co.za>
In-reply-to
Content
Elsewhere I have used "rough equivalent".

FWIW, the initializer defaulting to "None" is also an approximation.   It would be more technically correct to have "initializer = sentinel" where "sentinel = object()".   But of course this too would obfuscate the documentation which mainly aimed to clarify two sticky points:  1) the order of arguments to the function call (accm, x) vs (x, accm) and 2) that if an initializer isn't specified, the first value from the iterable is used.  These are the two issues that Guido found difficult to remember and caused reduce() to be banished from builtins.
History
Date User Action Args
2014-12-15 02:26:35rhettingersetrecipients: + rhettinger, georg.brandl, terry.reedy, docs@python, serhiy.storchaka
2014-12-15 02:26:35rhettingersetmessageid: <1418610395.24.0.967138011118.issue23049@psf.upfronthosting.co.za>
2014-12-15 02:26:35rhettingerlinkissue23049 messages
2014-12-15 02:26:34rhettingercreate