Message170493
| 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]) |
|