Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(12239)

#27873: multiprocessing.pool.Pool.map should take more than one iterable

Can't Edit
Can't Publish+Mail
Start Review
Created:
2 years, 11 months ago by ycm.jason
Modified:
2 years, 11 months ago
Reviewers:
python, naught101
CC:
tim.peters, rhettinger, berkerpeksag, davin, ycm.jason_gmail.com, naught101, flavianhautbois
Visibility:
Public.

Patch Set 1 #

Total comments: 2
Unified diffs Side-by-side diffs Delta from patch set Stats Patch
Doc/library/multiprocessing.rst View 1 chunk +6 lines, -2 lines 2 comments Download

Messages

Total messages: 2
davin
I'll add that I like the idea of the pointer to starmap here too. https://bugs.python.org/review/27873/diff/18683/Doc/library/multiprocessing.rst ...
2 years, 11 months ago #1
naught101
2 years, 11 months ago #2
https://bugs.python.org/review/27873/diff/18683/Doc/library/multiprocessing.rst
File Doc/library/multiprocessing.rst (left):

https://bugs.python.org/review/27873/diff/18683/Doc/library/multiprocessing.r...
Doc/library/multiprocessing.rst:2117: 
On 2016/09/29 04:13:41, davin wrote:
> Perhaps it be better to suggest how a map-style invocation using multiple
> iterables can be accomplished using a single iterable (via zip) here with
> Pool.map.  Rather than merely pointing out a difference, which might have
> already been noticed by the reader, we can be proactive in suggesting how to
> accomplish the same thing.

You can't use Pool.Map with a zip/list of lists. If you try to, it passes each
sub-list as the single first argument (which is not the same behaviour as map.
Or are you suggesting adding an example to Pool.starmap?
Sign in to reply to this message.

RSS Feeds Recent Issues | This issue
This is Rietveld 894c83f36cb7+