[issue24475] The docs never define what a pool "task" is

Change by Irit Katriel : -- components: +Library (Lib) versions: +Python 3.10, Python 3.11, Python 3.8, Python 3.9 -Python 2.7, Python 3.4, Python 3.5, Python 3.6 ___ Python tracker

[issue24475] The docs never define what a pool "task" is

Changes by Davin Potts : -- type: -> enhancement ___ Python tracker ___ ___

[issue24475] The docs never define what a pool task is

Daniel Neuberger added the comment: I second this. I was definitely confused at first and it took me a little while of googling to realize that jobs are not what one (at least me) would intuitively think they are. -- nosy: +Daniel Neuberger ___

[issue24475] The docs never define what a pool task is

Changes by Ned Deily n...@acm.org: -- nosy: +davin, sbt versions: -Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24475 ___

[issue24475] The docs never define what a pool task is

New submission from Zahari Dim: See: http://stackoverflow.com/questions/30943161/multiprocessing-pool-with-maxtasksperchild-produces-equal-pids The documentation never makes clear what a task in the context of Pool.map. At best, it says: This method chops the iterable into a number of chunks