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 <1408418871.9.0.670008345522.issue17140@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2014-08-19 03:27:52ncoghlansetrecipients: + ncoghlan, brandon-rhodes, sbt, Tilka, srodriguez
2014-08-19 03:27:51ncoghlansetmessageid: <1408418871.9.0.670008345522.issue17140@psf.upfronthosting.co.za>
2014-08-19 03:27:51ncoghlanlinkissue17140 messages
2014-08-19 03:27:51ncoghlancreate