Author r.david.murray
Recipients Julian, r.david.murray, twouters
Date 2013-06-02.03:27:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1370143650.77.0.189156185745.issue18111@psf.upfronthosting.co.za>
In-reply-to
Content
I don't think there's any other way to get a ValueError out of min/max, but I haven't actually looked at the code to check.  Of course, if we want people to rely on that, we'd need to document it.

'next's default is used to return a sentinel when the list is exhausted, not when it would otherwise raise a ValueError.  It is a somewhat related case, but is not exactly parallel.  The sentinel for next indicates the end of an ongoing process.  The proposed argument to min/max would *replace* an error with a sentinel value.
History
Date User Action Args
2013-06-02 03:27:30r.david.murraysetrecipients: + r.david.murray, twouters, Julian
2013-06-02 03:27:30r.david.murraysetmessageid: <1370143650.77.0.189156185745.issue18111@psf.upfronthosting.co.za>
2013-06-02 03:27:30r.david.murraylinkissue18111 messages
2013-06-02 03:27:30r.david.murraycreate