[issue5642] multiprocessing.Pool.map() docs slightly misleading

Georg Brandl added the comment: Fixed in r71149. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bug

[issue5642] multiprocessing.Pool.map() docs slightly misleading

New submission from James McDermott : I found the documentation for the multiprocessing.Pool.map() method to be a little misleading, because it claims to be equivalent to the built- in map(), but it's not quite. When the function to be applied takes just one argument, both map()s behave the s