On 9/3/05, Nick Coghlan <[EMAIL PROTECTED]> wrote: > Actually, it's an ordering quirk in the parser - the extended call syntax > stuff has to come last in the function call, which means we need to put the > keyword arguments at the front: > > Py> writeln(sep=', ', *(x*x for x in range(10))) > 0, 1, 4, 9, 16, 25, 36, 49, 64, 81 > > I personally believe keyword arguments should be allowed between *args and > **kwds at the call site, and keyword-only arguments after * in the function > definition, but the current behaviour has never bothered me enough for me to > look into what would be required to change it.
Same here. If anyone wants to give it a try, please go ahead! -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
