Nick Coghlan added the comment: 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. ---------- keywords: +easy nosy: +brandon-rhodes title: Provide a more obvious public ThreadPool API -> Document multiprocessing.pool.ThreadPool versions: +Python 3.5 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17140> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
