[issue22288] Incorrect Call grammar in documentation

Martijn Pieters added the comment: Fixed by revision 3ae399c6ecf6 -- resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue22288] Incorrect Call grammar in documentation

Changes by Martijn Pieters : -- hgrepos: -270 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue22288] Incorrect Call grammar in documentation

Martijn Pieters added the comment: Sigh, patch creation fails against a remove repository; I guess this only works for the default branch. Attached as a patch file instead. -- Added file: http://bugs.python.org/file36488/issue22288.patch ___ Python

[issue22288] Incorrect Call grammar in documentation

Changes by Martijn Pieters : Removed file: http://bugs.python.org/file36487/ffe77dc2979a.diff ___ Python tracker ___ ___ Python-bugs-list mail

[issue22288] Incorrect Call grammar in documentation

Changes by Martijn Pieters : -- keywords: +patch Added file: http://bugs.python.org/file36487/ffe77dc2979a.diff ___ Python tracker ___ ___

[issue22288] Incorrect Call grammar in documentation

Martijn Pieters added the comment: Proposed fix added in my fork. -- hgrepos: +270 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue22288] Incorrect Call grammar in documentation

New submission from Martijn Pieters: The changes for issue #3473 introduced a documentation bug. The Call expression grammar implies that f(*[1, 2], *[3, 4]) is allowed: | "*" `expression` ["," "*" `expression`] ["," "**" `expression`] I think Benjamin meant to use: | "*" `expression` ["," `k