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 dmacnet
Recipients Matt Spitz, dmacnet, josh.r, torsten
Date 2016-10-21.17:54:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
If each worker thread ties up other resources in an application, such as handles to server connections, conserving threads could have a significant impact. That's the situation for an application I am involved with.

I've written and tested a patch to make this change, using a second Queue for the worker threads to notify the executor in the main thread by sending a None when they finish a WorkItem and are therefore idle and ready for more work. It's a fairly simple patch. It does add a little more overhead to executing a job, inevitably. I can submit the patch if there's interest. Otherwise, perhaps the TODO comment in should be rewritten to explain why it's not worth doing.
Date User Action Args
2016-10-21 17:54:16dmacnetsetrecipients: + dmacnet, torsten, josh.r, Matt Spitz
2016-10-21 17:54:16dmacnetsetmessageid: <>
2016-10-21 17:54:16dmacnetlinkissue24882 messages
2016-10-21 17:54:16dmacnetcreate