EDIT:
I've removed the text for the original submission. Why? Because it was ugly as hell. No reason to keep it.
I will instead now link to the official copy of PEP 326.
On the occasion where I update it before it gets into CVS (as is wont to happen), I'll be placing a local copy on my machine, which would be available here. Please note, my machine gets turned off when I go to sleep.
Re: It's not really Some is it?
I don't see how making max and min more useful could possibly be any "worse" than that. I think it's really cool actually. max is a singleton that serves as a maximum value for any comparison that happens to have a callable that returns the maximum object in a sequence (read: something that supports the iterator protocol implicitly or explicitly).
I really think it's more attractive than adding members to cmp, which is a worse offense in my book. I don't know anywhere in (typical standard) Python where foo.bar is some useful type or singleton, except when foo is a module or package.
Re: It's not really Some is it?