Message132661
| Author |
jnoller |
| Recipients |
Albert.Strasheim, aljungberg, asksol, bquinlan, gdb, hongqn, jnoller, pitrou, vlasovskikh, vstinner |
| Date |
2011年03月31日.12:28:29 |
| SpamBayes Score |
4.6726354e-06 |
| Marked as misclassified |
No |
| Message-id |
<BANLkTinOxWYh9ZwKOF4kjx2zyQJOpnuF=g@mail.gmail.com> |
| In-reply-to |
<1301574338.12.0.437023762009.issue9205@psf.upfronthosting.co.za> |
| Content |
On Thu, Mar 31, 2011 at 8:25 AM, Antoine Pitrou <report@bugs.python.org> wrote:
>
> Antoine Pitrou <pitrou@free.fr> added the comment:
>
> Speaking of which, I wonder why we have both multiprocessing.Pool and concurrent.futures.ProcessPoolExecutor. They seem to fill the exact same needs, with different APIs...
>
Brian and I need to work on the consolidation we intend(ed) to occur
as people got comfortable with the APIs. My eventual goal is to remove
anything but the basic multiprocessing.Process/Queue stuff out of MP
and into concurrent.* and support threading backends for it. |
|