[issue32537] multiprocessing.pool.Pool.starmap_async - wrong parameter name

Pablo Galindo Salgado added the comment: Closed as is a duplicate of 31304. Thanks for reporting this! -- nosy: +pablogsal resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Update doc for starmap_async error_back kwarg

[issue32537] multiprocessing.pool.Pool.starmap_async - wrong parameter name

Ned Deily added the comment: This wouldn't qualify as a security problem so, if the problem no longer exists in 3.6, then this issue should be closed -- nosy: +ned.deily ___ Python tracker

[issue32537] multiprocessing.pool.Pool.starmap_async - wrong parameter name

Martin Panter added the comment: This was supposed to be fixed in 3.6+ by Issue 31304. In general, 3.5 only gets security fixes at this stage. I’m not sure if it is easy or worth back porting this. -- nosy: +martin.panter ___

[issue32537] multiprocessing.pool.Pool.starmap_async - wrong parameter name

New submission from Tilman Beck : The optional parameter for the error callback function is named "error_callback" not "error_back" -- assignee: docs@python components: Documentation files: bug.png messages: 309857 nosy: devnull, docs@python priority: normal