Skip to content

bpo-32306: Clarify c.f.Executor.map() documentation#4947

Merged
pitrou merged 1 commit into
python:masterfrom
pitrou:clarify_cf_map_doc
Dec 20, 2017
Merged

bpo-32306: Clarify c.f.Executor.map() documentation#4947
pitrou merged 1 commit into
python:masterfrom
pitrou:clarify_cf_map_doc

Conversation

@pitrou

@pitrou pitrou commented Dec 20, 2017

Copy link
Copy Markdown
Member

The built-in map() function collects function arguments lazily, but concurrent.futures.Executor.map() does so eagerly.

https://bugs.python.org/issue32306

The built-in map() function collects function arguments lazily, but
concurrent.futures.Executor.map() does so eagerly.
@miss-islington

Copy link
Copy Markdown
Contributor

Thanks @pitrou for the PR 🌮🎉.. I'm working now to backport this PR to: 3.6.
🐍🍒⛏🤖 I'm not a witch! I'm not a witch!

@pitrou pitrou deleted the clarify_cf_map_doc branch December 20, 2017 18:06
miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Dec 20, 2017
The built-in map() function collects function arguments lazily, but concurrent.futures.Executor.map() does so eagerly.
(cherry picked from commit a7a751d)
@bedevere-bot

Copy link
Copy Markdown

GH-4948 is a backport of this pull request to the 3.6 branch.

pitrou pushed a commit that referenced this pull request Dec 20, 2017
The built-in map() function collects function arguments lazily, but concurrent.futures.Executor.map() does so eagerly.
(cherry picked from commit a7a751d)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants