[Python-ideas] Better integration of multiprocessing with asyncio

[Dan O'Reilly]

For what it's worth, I ended up writing a module that takes the "threads on
top of regular multiprocessing" approach to integrate the two:
https://github.com/dano/aioprocessing.

Re-implementing multiprocessing to use asyncio internally, while an
interesting exercise, would require a very large amount of effort both to
implement and maintain alongside the current multiprocessing module. I'm
not sure it's really worth it when using threads on top of multiprocessing
gives you the same effect without requiring you to basically re-implement
large parts of the multiprocessing module.

Anyway, we'll see if it ends up getting much use...

On Sat, Jul 26, 2014 at 11:48 PM, Ryan Hiebert <ryan at ryanhiebert.com> wrote:

>
> On Jul 26, 2014, at 10:43 PM, Guido van Rossum <guido at python.org> wrote:
>
> I'm going to go out on a limb here and say that it feels too early to me.
> First someone has to actually solve this problem well as a 3rd party
> package before we can talk about adding it to the asyncio package. It
> doesn't actually sound like Billiards has adapted to asyncio yet (not that
> I have any idea what Billiards is -- it sounds like a fork of
> multiprocessing actually?).
>
>
> Yep, Billiard is a fork of multiprocessing:
> https://pypi.python.org/pypi/billiard
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-ideas/attachments/20141008/b122947b/attachment-0001.html>