Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > Maybe yes, the easier but probably harmless solution is to change the > documentation and point out that "in general, you can't". Maybe this > somehow leans towards promoting a bug to the rank of feature? ;-)
The language spec is stuck between saying what the abstract Python language is supposed to do, and describing what CPython precisely does. You shouldn't use keyword arguments to pass non-optional positional arguments, IMO, but the text describes precisely what happens if you do - for Python functions. The more vague specification then shouldn't say "you can't" (because that would indicate that you get an exception when you try), but "it's unspecified", then going on to say what CPython happens to do in some release. __________________________________ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2677> __________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
