[issue11777] Executor.map does not submit futures until iter.next() is called

Éric Araujo added the comment: Just a bystander remark: when you use present in the commit message and Misc/NEWS entry (like in “Executor.map does not submit futures until iter.next() is called”), I don’t know whether it is the behavior being fixed (“X used to do Y”) or the new, correct behav

[issue11777] Executor.map does not submit futures until iter.next() is called

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

[issue11777] Executor.map does not submit futures until iter.next() is called

Roundup Robot added the comment: New changeset 126353bc7e94 by Brian Quinlan in branch 'default': Issue #11777: Executor.map does not submit futures until iter.next() is called http://hg.python.org/cpython/rev/126353bc7e94 -- nosy: +python-dev ___ Py

[issue11777] Executor.map does not submit futures until iter.next() is called

Brian Quinlan added the comment: Nice catch. I hadn't noticed that the docs are lying :-) -- ___ Python tracker ___ ___ Python-bugs-l

[issue11777] Executor.map does not submit futures until iter.next() is called

ysj.ray added the comment: Got it. Seems the behavior is not consist with the Executor.map() function: "The returned iterator raises a TimeoutError if __next__() is called and the result isn't available after timeout seconds from ***the original call to map()***" --

[issue11777] Executor.map does not submit futures until iter.next() is called

Brian Quinlan added the comment: I think that it surprising behavior, especially considering that asking for the *first* element in the iterator causes *all* of the futures to be created. -- ___ Python tracker __

[issue11777] Executor.map does not submit futures until iter.next() is called

ysj.ray added the comment: Isn't this the supposed behavior? -- nosy: +ysj.ray ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue11777] Executor.map does not submit futures until iter.next() is called

New submission from Brian Quinlan : from concurrent import futures with futures.ThreadPoolExecutor(max_workers=5) as e: e.map(print, range(10)) # No output -- assignee: bquinlan components: Library (Lib) messages: 133104 nosy: bquinlan priority: normal severity: normal status: open t