[issue24446] imap and map inconsistent behaviour

2015-06-13 Thread Ned Deily
Ned Deily added the comment: Also note that the behavior of map() in Python 3 has been changed to also stop with the termination of the shortest iterator. https://docs.python.org/3.4/whatsnew/3.0.html#views-and-iterators-instead-of-lists -- ___ Pyth

[issue24446] imap and map inconsistent behaviour

2015-06-13 Thread Ned Deily
Ned Deily added the comment: This is a documented behavior difference in itertools.imap: "If function is set to None, then imap() returns the arguments as a tuple. Like map() but stops when the shortest iterable is exhausted instead of filling in None for shorter iterables. The reason for the

[issue24446] imap and map inconsistent behaviour

2015-06-13 Thread Ernesto Alfonso
New submission from Ernesto Alfonso: itertools.imap and map in Python 2.7 produces inconsistent behaviour when mapping the null (None) function over multiple sequences. >>> [a for a in map(None, list("abcd"), range(3))] [('a', 0), ('b', 1), ('c', 2), ('d', None)] >>> from itertools import im