This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author davin
Recipients davin, pablogsal, pitrou, steve.dower, vstinner
Date 2019-09-10.15:50:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Thanks to Pablo's good work with implementing the use of multiprocessing's Process.sentinel, the logic for handling PoolWorkers that die has been centralized into Pool._maintain_pool().  If _maintain_pool() can also identify which job died with the dead PoolWorker, then it should be possible to put a corresponding message on the outqueue to indicate an exception occurred but pool can otherwise continue its work.

The question of whether should expose a timeout parameter deserves a separate discussion and should not be considered a path forward on this issue as it would require that users always specify and somehow know beforehand how long it should take for results to be returned from workers.  Exposing the timeout control may have other practical benefits elsewhere but not here.
Date User Action Args
2019-09-10 15:50:24davinsetrecipients: + davin, pitrou, vstinner, steve.dower, pablogsal
2019-09-10 15:50:24davinsetmessageid: <>
2019-09-10 15:50:24davinlinkissue38084 messages
2019-09-10 15:50:24davincreate