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 ncoghlan
Recipients Tilka, brandon-rhodes, ncoghlan, sbt, srodriguez
Date 2014-08-19.03:27:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
After a question from Brandon Rhodes, I noticed that ThreadPool is actually listed in multiprocess.pool.__all__.

So rather than doing anything more dramatic, we should just document the existing multiprocessing feature.

As Richard says, the concurrent.futures Executor already provides a general purpose thread and process pooling model, and when that isn't appropriate, something like asyncio or gevent may actually be a better fit anyway.
Date User Action Args
2014-08-19 03:27:52ncoghlansetrecipients: + ncoghlan, brandon-rhodes, sbt, Tilka, srodriguez
2014-08-19 03:27:51ncoghlansetmessageid: <>
2014-08-19 03:27:51ncoghlanlinkissue17140 messages
2014-08-19 03:27:51ncoghlancreate