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 chris.jerdonek
Recipients asvetlov, chris.jerdonek, docs@python, eric.araujo, ezio.melotti, georg.brandl, python-dev
Date 2012-09-14.17:18:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1347643144.43.0.224553762668.issue15831@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks, Ezio!

By the way, I didn't do a thorough check, but I noticed this difference in the 2.7 application of the patch.  The *key* argument for max() needs to be marked keyword-only.  This difference doesn't exist for the min() function.  Or are we not using the "bare *" notation in the 2.7 docs?  If not, the min() docs need to be changed instead (and possibly in several other places).

Default branch:

-.. function:: max(iterable[, args...], *[, key])
+.. function:: max(iterable, *[, key])
+              max(arg1, arg2, *args[, key])

2.7 branch:

-.. function:: max(iterable[, args...][key])
+.. function:: max(iterable[, key])
+              max(arg1, arg2, *args[, key])
History
Date User Action Args
2012-09-14 17:19:04chris.jerdoneksetrecipients: + chris.jerdonek, georg.brandl, ezio.melotti, eric.araujo, asvetlov, docs@python, python-dev
2012-09-14 17:19:04chris.jerdoneksetmessageid: <1347643144.43.0.224553762668.issue15831@psf.upfronthosting.co.za>
2012-09-14 17:18:43chris.jerdoneklinkissue15831 messages
2012-09-14 17:18:43chris.jerdonekcreate