[issue27873] multiprocessing.pool.Pool.map should take more than one iterable

Kyle Stanley added the comment: > Can this issue be closed, I see it was merged successfully? Yep, I'll go ahead and close the issue now. Thanks for the reminder; I got caught up in a few other projects. -- stage: patch review -> resolved status: open -> closed

[issue27873] multiprocessing.pool.Pool.map should take more than one iterable

Ido Michael added the comment: Can this issue be closed, I see it was merged successfully? -- ___ Python tracker ___ ___

[issue27873] multiprocessing.pool.Pool.map should take more than one iterable

miss-islington added the comment: New changeset baf07395eaa77e515ddfa1d3f42785d50b4d2889 by Miss Islington (bot) in branch '3.8': bpo-27873: Update docstring for multiprocessing.Pool.map (GH-17436) https://github.com/python/cpython/commit/baf07395eaa77e515ddfa1d3f42785d50b4d2889 --

[issue27873] multiprocessing.pool.Pool.map should take more than one iterable

miss-islington added the comment: New changeset 55a7046471e19843a68d4a1a15252fd197bb6913 by Miss Islington (bot) in branch '3.7': bpo-27873: Update docstring for multiprocessing.Pool.map (GH-17436) https://github.com/python/cpython/commit/55a7046471e19843a68d4a1a15252fd197bb6913 --

[issue27873] multiprocessing.pool.Pool.map should take more than one iterable

Change by miss-islington : -- pull_requests: +16940 pull_request: https://github.com/python/cpython/pull/17459 ___ Python tracker ___

[issue27873] multiprocessing.pool.Pool.map should take more than one iterable

Change by miss-islington : -- pull_requests: +16939 pull_request: https://github.com/python/cpython/pull/17458 ___ Python tracker ___

[issue27873] multiprocessing.pool.Pool.map should take more than one iterable

miss-islington added the comment: New changeset eb48a451e3844185b9a8751c9badffbddc89689d by Miss Islington (bot) (An Long) in branch 'master': bpo-27873: Update docstring for multiprocessing.Pool.map (GH-17436) https://github.com/python/cpython/commit/eb48a451e3844185b9a8751c9badffbddc89689d

[issue27873] multiprocessing.pool.Pool.map should take more than one iterable

Change by AnLong : -- pull_requests: +16916 pull_request: https://github.com/python/cpython/pull/17436 ___ Python tracker ___ ___

[issue27873] multiprocessing.pool.Pool.map should take more than one iterable

Change by AnLong : -- pull_requests: +16853 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/17367 ___ Python tracker ___

[issue27873] multiprocessing.pool.Pool.map should take more than one iterable

Kyle Stanley added the comment: > Is it still open? What else needs to be done? Yes, this patch needs to be translated into a GitHub PR. See https://devguide.python.org/pullrequest/ for more information on our PR workflow if you're not already familiar with it. Since naught101 wrote a

[issue27873] multiprocessing.pool.Pool.map should take more than one iterable

Ido Michael added the comment: Hey, Is it still open? What else needs to be done? Ido -- nosy: +Ido Michael ___ Python tracker ___

[issue27873] multiprocessing.pool.Pool.map should take more than one iterable

Flavian Hautbois added the comment: Are you going to open a PR for this patch? I think that would be a nice addition -- nosy: +flavianhautbois ___ Python tracker ___

[issue27873] multiprocessing.pool.Pool.map should take more than one iterable

Davin Potts added the comment: @naught101: Thanks for the wording change -- I think your suggested doc change will be a good one. I've added a comment which you can access via the "review" link to the right of the link for your mp.map.starmap.patch attachment. --

[issue27873] multiprocessing.pool.Pool.map should take more than one iterable

naught101 added the comment: Here you go. -- keywords: +patch Added file: http://bugs.python.org/file44851/mp.map.starmap.patch ___ Python tracker ___

[issue27873] multiprocessing.pool.Pool.map should take more than one iterable

naught101 added the comment: OK, one question, is Pool.map preferable to Pool.starmap in any particular cases? -- ___ Python tracker ___

[issue27873] multiprocessing.pool.Pool.map should take more than one iterable

Berker Peksag added the comment: > What is the process? hg clone cpython, and make a patch from that and post it > here? Yes, it's exactly what you just described :) See https://docs.python.org/devguide/index.html for details. > Or is there some pull-request style process available? Not

[issue27873] multiprocessing.pool.Pool.map should take more than one iterable

naught101 added the comment: Happy to. What is the process? hg clone cpython, and make a patch from that and post it here? Or is there some pull-request style process available? -- ___ Python tracker

[issue27873] multiprocessing.pool.Pool.map should take more than one iterable

Berker Peksag added the comment: I think we can add a note for starmap() in the following sentence: > [...] (it supports only one iterable argument though). (Quoted from https://docs.python.org/3/library/multiprocessing.html#multiprocessing.pool.Pool.map) Would you like to write a patch?

[issue27873] multiprocessing.pool.Pool.map should take more than one iterable

naught101 added the comment: It would be helpful if the docs at https://docs.python.org/3/library/multiprocessing.html#multiprocessing.pool.Pool.map and in `help(Pool.map)` mentioned starmap in a "see also" section at the bottom. -- nosy: +naught101

[issue27873] multiprocessing.pool.Pool.map should take more than one iterable

Tim Peters added the comment: Note that `Pool` grew `starmap()` and `starmap_async()` methods in Python 3.3 to (mostly) address this. The signature difference from the old builtin `map()` remains regrettable. Note that the `Pool` version differs from the `concurrent.futures` version of

[issue27873] multiprocessing.pool.Pool.map should take more than one iterable

Raymond Hettinger added the comment: -0 We need better motivation than "that is was map() does". Instead, are should look at whether there are compelling use cases and its impact on the complexity of the multiprocessing implementation. I usually just prezip my data and it works fine.

[issue27873] multiprocessing.pool.Pool.map should take more than one iterable

New submission from Jason Yu: Hello all, The official doc describes `Pool.map(func, iterable[, chunksize])` as "A parallel equivalent of the map() built-in function.". Since the function signature of `map` is `map(function, iterable, ...)`, I hereby suggest that `Pool.map` should change