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 iunknwn
Recipients Matt Spitz, bquinlan, dmacnet, iunknwn, josh.r, pitrou, tomMoral, torsten
Date 2018-04-13.19:36:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The existing behavior seems strange (and isn't well documented). The code had a TODO comment from bquinlan to implement idle thread recycling, so that was why I made the change. 

That said, if threads are cheap, why not just create all the work threads on initialization, and then remove all the logic entirely?

Also, regarding the executor and thread-safety, there's an example in the current docs showing a job being added to the executor from a worker thread (it's part of the example on deadlocks, but it focuses on max worker count, not on the executor's thread-safety).
Date User Action Args
2018-04-13 19:36:55iunknwnsetrecipients: + iunknwn, bquinlan, pitrou, torsten, josh.r, Matt Spitz, tomMoral, dmacnet
2018-04-13 19:36:55iunknwnsetmessageid: <>
2018-04-13 19:36:55iunknwnlinkissue24882 messages
2018-04-13 19:36:54iunknwncreate