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 asksol
Recipients asksol, gdb, jnoller
Date 2010-07-12.20:08:28
SpamBayes Score 0.0513083
Marked as misclassified No
Message-id <>
termination.patch, in the result handler you've added:

   while cache and thread._state != TERMINATE and not failed

why are you terminating the second pass after finding a failed process?

Unpickleable errors and other errors occurring in the worker body are not exceptional cases, at least not now that the pool is supervised by _handle_workers. I think the result should be set also in this case, so the user can inspect the exception after the fact.

I have some other suggestions too, so I will review this patch tomorrow.

For shutdown.patch, I thought this only happened in the worker handler, but you've enabled this for the result handler too? I don't care about the worker handler, but with the result handler I'm worried that I don't know what ignoring these exceptions actually means. For example, is there a possibility that we may lose results at shutdown?
Date User Action Args
2010-07-12 20:08:35asksolsetrecipients: + asksol, jnoller, gdb
2010-07-12 20:08:34asksolsetmessageid: <>
2010-07-12 20:08:28asksollinkissue9205 messages
2010-07-12 20:08:28asksolcreate