[issue43306] Error in multiprocessing.Pool's initializer doesn't stop execution

Aaron added the comment: What should the behavior be if an exception is raised in a pool worker during bootstrapping / initialization function execution? I think an exception should be raised in the process owning the Pool, and in the fix I'm tinkering around with I just raise a

[issue43306] Error in multiprocessing.Pool's initializer doesn't stop execution

Aaron added the comment: I ran into this bug answering this question on Stack Overflow: https://stackoverflow.com/questions/68890437/cannot-use-result-from-multiprocess-pool-directly I have minimized the code required to replicate the behavior, but it boils down to: when using "spawn" to

[issue43306] Error in multiprocessing.Pool's initializer doesn't stop execution

Terry J. Reedy added the comment: Can you add a minimal example with the ignore behavior? -- assignee: docs@python -> nosy: +davin, pitrou, terry.reedy ___ Python tracker

[issue43306] Error in multiprocessing.Pool's initializer doesn't stop execution

New submission from Dávid Nemeskey : There is an inconsistency in how multiprocessing.Pool handles exceptions thrown in the workers: - exceptions raised by the mapped function stop execution right away - exceptions raised in an initializer are ignored and the pool continues spawning new