On Mon, May 01, 2006, Edward Loper wrote: > > But is it necessary to syntactically *enforce* that the arguments be > used as keywords? I.e., why not just document that the arguments should > be used as keyword arguments, and leave it at that. If users insist on > using them positionally, then their code will be less readable, and > might break if you decide to change the order of the parameters, but > we're all consenting adults. (And if you *do* believe that the > parameters should all be passed as keywords, then I don't see any reason > why you'd ever be motivated to change their order.) IIRC, part of the motivation for this is to make it easier for super() to work correctly. -- Aahz (aahz at pythoncraft.com) <*> http://www.pythoncraft.com/ "Argue for your limitations, and sure enough they're yours." --Richard Bach
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