[issue12531] documentation index entries for * and **

Roundup Robot added the comment: New changeset 8862ec62f9ee by Ezio Melotti in branch '3.2': #12531: Fix spaces and markup. http://hg.python.org/cpython/rev/8862ec62f9ee New changeset b47c9982506c by Ezio Melotti in branch 'default': #12531: merge with 3.2. http://hg.python.org/cpython/rev/b47c

[issue12531] documentation index entries for * and **

Changes by Éric Araujo : -- stage: patch review -> committed/rejected ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue12531] documentation index entries for * and **

Changes by Eli Bendersky : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue12531] documentation index entries for * and **

Roundup Robot added the comment: New changeset a8aa918041c2 by Eli Bendersky in branch '3.2': Issue #12531: add index entries to documentation of * and ** in function calls http://hg.python.org/cpython/rev/a8aa918041c2 New changeset 221ca00121ef by Eli Bendersky in branch 'default': Merge from

[issue12531] documentation index entries for * and **

Eli Bendersky added the comment: Éric - when I was just starting contributing patches to Python, I was strictly disciplined by veteran devs to stay within 80 chars no matter what :-) -- ___ Python tracker ___

[issue12531] documentation index entries for * and **

Éric Araujo added the comment: Looks good to me. One tip for commits: it’s often better to let a line exceed 80 characters in order to make for a smaller diff. Here, only one word was changed but four lines were marked as changed, which makes reviews longer. Lines are rewrapped when doing

[issue12531] documentation index entries for * and **

Eli Bendersky added the comment: I've committed a fix into 2.7, taking Terry's advice ("in function calls" subsection instead of "statement") and Eric's sequence/iterable correction into account. If this looks OK, I will commit a similar fix to the 3.x branches as well. -- _

[issue12531] documentation index entries for * and **

Roundup Robot added the comment: New changeset 8328fe952303 by Eli Bendersky in branch '2.7': Issue #12531: add index entries to documentation of * and ** in function calls http://hg.python.org/cpython/rev/8328fe952303 -- nosy: +python-dev ___ Python

[issue12531] documentation index entries for * and **

Eli Bendersky added the comment: Peter, would you like to submit a corrected patch? -- ___ Python tracker ___ ___ Python-bugs-list ma

[issue12531] documentation index entries for * and **

Terry J. Reedy added the comment: > expression must evaluate to a sequence. To be clear, Eli quoted the doc correctly and Eric correctly suggested that 'sequence' needs to be updated to 'iterable' (in at least two places). Since the patch for this issue will be adding something just above, it

[issue12531] documentation index entries for * and **

Terry J. Reedy added the comment: I would not propose to do everything in one grand patch as it would be way too much to review all at once. A somewhat separate subissue is whether there should be however many separate issues over the next however many years or one master issue with multiple

[issue12531] documentation index entries for * and **

Changes by Éric Araujo : -- nosy: +ericsnow, terry.reedy versions: +Python 2.7, Python 3.2 ___ Python tracker ___ ___ Python-bugs-list

[issue12531] documentation index entries for * and **

Éric Araujo added the comment: > [...] If the syntax *expression appears in the function call, > expression must evaluate to a sequence. An iterable :) -- nosy: +eric.araujo -ericsnow, terry.reedy versions: -Python 2.7, Python 3.2 ___ Python tracke

[issue12531] documentation index entries for * and **

Eli Bendersky added the comment: Peter, doesn't your patch also refer to the meaning of * and ** in function definitions? I would argue that the missing reference is to a paragraph further down: [...] If the syntax *expression appears in the function call, expression must evaluate to a

[issue12531] documentation index entries for * and **

Changes by Eric Snow : -- nosy: +ericsnow ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue12531] documentation index entries for * and **

Terry J. Reedy added the comment: This is just the tip of the iceberg as far as needed symbol index entries goes. Nearly 3 years ago, I wrote a Python 3 symbol glossary "Python3 Syntax Symbol Uses" that was complete as far as I knew then. I think most of the entries there should have a corres

[issue12531] documentation index entries for * and **

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue12531] documentation index entries for * and **

Changes by Eli Bendersky : -- nosy: +eli.bendersky ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue12531] documentation index entries for * and **

New submission from Peter Eisentraut : The existing documentation index entries for * and ** only point to their use in function definitions but not to their use in function calls. I was looking for the latter, and it was difficult to find without this. Here is a small patch to add the addit