[issue29108] Python 3.6.0 multiprocessing map_async callback

Jose Miguel Colella added the comment: Hello David, Thanks for your response. Improvements to the documentation could clear this misunderstanding. I had initially believed that after transforming with the function passed to the map, it would use the callback on each of the result arguments. J

[issue29108] Python 3.6.0 multiprocessing map_async callback

Davin Potts added the comment: This appears to be working as designed. The purpose of the callback is to receive a single argument (nominally, the ready result from the map operation) and perform its task (whatever it may be) very quickly so as not to further delay the handing back of results

[issue29108] Python 3.6.0 multiprocessing map_async callback

Changes by Ned Deily : -- nosy: +davin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/

[issue29108] Python 3.6.0 multiprocessing map_async callback

Jose Miguel Colella added the comment: The result is: Here: [1, 4, 9] [1, 4, 9] -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue29108] Python 3.6.0 multiprocessing map_async callback

New submission from Jose Miguel Colella: Hello I am trying to use the callback for the map_async method for Pool, but have found a bug. In the below code, only the print statement is carried out, the return is completely ignored. Is this working as designed or is this a bug? from multiprocessi