[issue36620] Documentation missing parameter for Itertools.zip_longest
New submission from Charles Merriam <charles.merriam@gmail.com>: On page: https://docs.python.org/3.8/library/itertools.html In the heading summary, in the "Iterators terminating on the shortest input sequence:" section, in the "zip_longest()" table row, in the "Arguments" column, the text "p, q, ..." should be "p, q, ... [, fillvalue=None]" ---------- assignee: docs@python components: Documentation messages: 340107 nosy: CharlesMerriam, docs@python priority: normal severity: normal status: open title: Documentation missing parameter for Itertools.zip_longest type: enhancement versions: Python 3.8 _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue36620> _______________________________________
Change by SilentGhost <ghost.adh@runbox.com>: ---------- stage: -> needs patch versions: +Python 3.7 _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue36620> _______________________________________
Cheryl Sabella <cheryl.sabella@gmail.com> added the comment: Good catch! In the same section, accumulate() is missing the `initial` argument. Would you be interested in submitting a pull request for this? ---------- nosy: +cheryl.sabella _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue36620> _______________________________________
Charles Merriam <charles.merriam@gmail.com> added the comment: Hi Cheryl, No. I've dealt with the Team Python long cycles for random pull requests before. Charles On Fri, Apr 12, 2019 at 2:27 PM Cheryl Sabella <report@bugs.python.org> wrote:
Cheryl Sabella <cheryl.sabella@gmail.com> added the comment:
Good catch! In the same section, accumulate() is missing the `initial` argument.
Would you be interested in submitting a pull request for this?
---------- nosy: +cheryl.sabella
_______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue36620> _______________________________________
---------- nosy: +Charles.Merriam _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue36620> _______________________________________
Change by Karthikeyan Singaravelan <tir.karthi@gmail.com>: ---------- nosy: +rhettinger _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue36620> _______________________________________
Cheryl Sabella <cheryl.sabella@gmail.com> added the comment: Thanks, Charles. I'm going to assign this to @Mariatta for the sprints. ---------- assignee: docs@python -> Mariatta nosy: +Mariatta _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue36620> _______________________________________
Ying Wang <yingw787.personal@gmail.com> added the comment: I would like to take a stab at this as a first-time CPython contributor. ---------- nosy: +Ying Wang _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue36620> _______________________________________
Change by Roundup Robot <devnull@psf.upfronthosting.co.za>: ---------- keywords: +patch pull_requests: +13121 stage: needs patch -> patch review _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue36620> _______________________________________
Raymond Hettinger <raymond.hettinger@gmail.com> added the comment: Sorry, I don't want to do this in the summary table. The goal of the table is to provide a minimal overview to help select the appropriate itertool and to provide a fast link to the details given below. ---------- assignee: Mariatta -> rhettinger _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue36620> _______________________________________
Ying Wang <yingw787.personal@gmail.com> added the comment: @rhettinger should this issue be closed if no action is to be taken? If so, should I manually close the pull request referencing this issue, or will that be automatically handled by the Python bug tracker? ---------- _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue36620> _______________________________________
Raymond Hettinger <raymond.hettinger@gmail.com> added the comment: I'll take care of it. Thank you. ---------- stage: patch review -> resolved status: open -> closed _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue36620> _______________________________________
participants (7)
-
Charles Merriam -
Cheryl Sabella
-
Karthikeyan Singaravelan
-
Raymond Hettinger
-
Roundup Robot
-
SilentGhost
-
Ying Wang