> > If we assume that no one is calling min or max without arguments in > > order to raise a TypeError (which seems like a reasonable assumption), > > then replacing the TypeError exception for behavior 1 with the following > > seems reasonable: > > min() -> Min > > max() -> Max > > I consider that behavior Unreasonable. What's reasonable is > > min() -> Max > max() -> Min That it is possible to disagree about whether min() should return Min or Max is enough to veto this idea. --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4