[issue3473] In function call, keyword arguments could follow *args
Martijn Pieters added the comment: The documentation change in this patch introduced a bug in the Call grammar: | * `expression` [, * `expression`] [, ** `expression`] instead of | * `expression` [, `keyword_arguments`] [, ** `expression`] giving the impression that `*expression` is allowed twice. -- nosy: +mjpieters ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3473 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3473] In function call, keyword arguments could follow *args
Roundup Robot added the comment: New changeset 3ae399c6ecf6 by Benjamin Peterson in branch '2.7': correct call grammar error (#3473) http://hg.python.org/cpython/rev/3ae399c6ecf6 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3473 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3473] In function call, keyword arguments could follow *args
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment: The compiler package was fixed some time ago with r65891 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3473 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3473] In function call, keyword arguments could follow *args
Changes by Jesús Cea Avión [EMAIL PROTECTED]: -- nosy: +jcea ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3473 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3473] In function call, keyword arguments could follow *args
Barry A. Warsaw [EMAIL PROTECTED] added the comment: Guido's approved it, so please go ahead and add it before beta 3. -- resolution: - accepted ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3473 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3473] In function call, keyword arguments could follow *args
Benjamin Peterson [EMAIL PROTECTED] added the comment: Applied for 2.6 in r65872. -- status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3473 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3473] In function call, keyword arguments could follow *args
Benjamin Peterson [EMAIL PROTECTED] added the comment: Done for py3k in r65877. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3473 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3473] In function call, keyword arguments could follow *args
Benjamin Peterson [EMAIL PROTECTED] added the comment: Now test_compiler is breaking for us because the compiler package can't handle the change. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3473 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3473] In function call, keyword arguments could follow *args
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment: Barry, is it still time for this to be included in 2.6b3? Guido already approved the idea: http://mail.python.org/pipermail/python-3000/2008-July/014506.html -- assignee: rhettinger - amaury.forgeotdarc nosy: +barry ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3473 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3473] In function call, keyword arguments could follow *args
Georg Brandl [EMAIL PROTECTED] added the comment: Ping! -- nosy: +georg.brandl ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3473 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3473] In function call, keyword arguments could follow *args
Terry J. Reedy [EMAIL PROTECTED] added the comment: Another use case: upon reading A.Baxter's Porting to 3 talk, I realized, slightly generalizing from his example, that print(s.join(map(str,it))) == print(*it,sep=s) -- or would, except that it currently has to be written non-intuitively as print(sep=s,*it), which I might not have tried except for knowing about this issue. Given that many have problems with .join and that most uses are to produce immediate output not otherwise processed, I think having the replacement work in the way many would expect would be a win. So I hope this makes the next beta. -- nosy: +tjreedy ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3473 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3473] In function call, keyword arguments could follow *args
Raymond Hettinger [EMAIL PROTECTED] added the comment: +1 for applying to 2.6. izip_longest() is a perfect example of where it's important. -- nosy: +rhettinger ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3473 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3473] In function call, keyword arguments could follow *args
Changes by Amaury Forgeot d'Arc [EMAIL PROTECTED]: -- keywords: +patch Added file: http://bugs.python.org/file11010/kwargs30.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3473 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3473] In function call, keyword arguments could follow *args
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment: Patches for both versions are attached. Added file: http://bugs.python.org/file11011/kwargs26.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3473 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3473] In function call, keyword arguments could follow *args
Benjamin Peterson [EMAIL PROTECTED] added the comment: The patches look good to me. -- nosy: +benjamin.peterson ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3473 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3473] In function call, keyword arguments could follow *args
Nick Coghlan [EMAIL PROTECTED] added the comment: I'll have a look at this in the next day or two. -- nosy: +ncoghlan ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3473 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3473] In function call, keyword arguments could follow *args
New submission from Amaury Forgeot d'Arc [EMAIL PROTECTED]: functions with keyword-only arguments have this form: def f(x, *args, y): pass parameters can appear after the *arg, they are required to be passed by keyword. It would be more consistent to allow this function call: f(X, *ARGS, y=Y) This is invalid syntax, *ARGS is required to be at the end of the arguments, together with an eventual **KWARGS. This restriction should be lifted. See the use case in http://mail.python.org/pipermail/python-3000/2008-July/014437.html -- assignee: amaury.forgeotdarc messages: 70449 nosy: amaury.forgeotdarc severity: normal status: open title: In function call, keyword arguments could follow *args versions: Python 3.0 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3473 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3473] In function call, keyword arguments could follow *args
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment: Should this apply to 2.6 as well? See r65321, I find the last line easier to read when arguments are in this order. def grouper(n, iterable, fillvalue=None): args = [iter(iterable)] * n return izip_longest(*args, fillvalue=fillvalue) On the cons side, keyword-only arguments don't exist in 2.6, so the consistency with function definition syntax does not apply. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3473 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
