This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: itertools' docs put izip_longest in the "terminating on the shortest input sequence" section
Type: Stage:
Components: Documentation Versions: Python 3.1, Python 3.2, Python 2.7
process
Status: closed Resolution: wont fix
Dependencies: Superseder:
Assigned To: docs@python Nosy List: abeld, docs@python, rhettinger
Priority: normal Keywords:

Created on 2010-10-12 09:20 by abeld, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (2)
msg118407 - (view) Author: Daniel Abel (abeld) Date: 2010-10-12 09:20
Both the 2.x and 3.x documentation for itertools has izip_longest (zip_longest for 3.x)  in the "Iterators terminating on the shortest input sequence" section. However, according to izip_longest's documentation, it terminates when the _longest_ iterator is exhausted.

Possible fixes might be:
- put izip_longest in a new "Iterators terminating on the longest input sequence" section
- rename section to "Iterators terminating on one of the input sequences"
msg118452 - (view) Author: Raymond Hettinger (rhettinger) * (Python committer) Date: 2010-10-12 18:17
I saw that when I put in in. 
It doesn't fit the overall category
but it does belong in the same general
grouping and the notes make the semantics clear,
so there is no harm in it and I like the current
presentation better than the alternatives.
History
Date User Action Args
2022-04-11 14:57:07adminsetgithub: 54276
2010-10-12 18:17:43rhettingersetstatus: open -> closed
2010-10-12 18:17:07rhettingersetresolution: wont fix
messages: + msg118452
2010-10-12 17:17:12eric.araujosetnosy: + rhettinger

versions: - Python 3.3
2010-10-12 09:20:13abeldcreate