[Baypiggies] FWD: Parallelism in one line

[Guido van Rossum]

Apart from its unavailability in Python 2, it would seem that the
Executor abstraction (PEP 3148, concurrent.futures.Executor -- there's
a thread and a multiprocessing variant) does the same thing and is
just as easy to use. Isn't it?
http://www.python.org/dev/peps/pep-3148/#executor

It's probably even been backported to Python 2 by some kind soul. :-)

On Thu, Jan 2, 2014 at 8:11 PM, Martin Falatic <martin at falatic.com> wrote:
> Definitely interesting, but the discussion of this article on Reddit gives
> further food for thought on the pros and cons of using this strategy:
>
> http://www.reddit.com/r/Python/comments/1tyzw3/parallelism_in_one_line/
>
> Note that the article's author is participating in that discussion.
>
> A related thread (also with some discussion by the author) can be found here:
>
> http://www.reddit.com/r/programming/comments/1u37v2/parallelism_in_one_line/
>
>  - Marty
>
>
>
> On Wed, January 1, 2014 07:36, Aahz wrote:
>> Raise your hand if you knew that multiprocessing.dummy provided a
>> multiprocessing API wrapper around threading.Thread:
>>
>> https://medium.com/p/40e9b2b36148
>>
>>
>> Also shows how multiprocessing's map() is the easiest way to do
>> concurrent programming. --
>> Aahz (aahz at pythoncraft.com)           <*>
>> http://www.pythoncraft.com/
>>
>>
>> A house is a machine to keep your cat dry.
>> _______________________________________________
>> Baypiggies mailing list
>> Baypiggies at python.org
>> To change your subscription options or unsubscribe:
>> https://mail.python.org/mailman/listinfo/baypiggies
>>
>>
>
>
> _______________________________________________
> Baypiggies mailing list
> Baypiggies at python.org
> To change your subscription options or unsubscribe:
> https://mail.python.org/mailman/listinfo/baypiggies



-- 
--Guido van Rossum (python.org/~guido)