➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author neologix
Recipients Christian.Tismer, Claudiu.Popa, aleax, kristjan.jonsson, lemburg, neologix, pitrou, r.david.murray, rhettinger, tim.peters, tinchester
Date 2014-07-21.06:54:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM3fT1a_8c0Juh_jMT9wJ33et5pCGgwRjdENZtP5O=q+KA@mail.gmail.com>
In-reply-to <1405896509.62.0.303578140414.issue22013@psf.upfronthosting.co.za>
Content 
> Tin Tvrtković added the comment:
>
> For your examples, my first instinct would be to use a thread pool executor. It's a nice high level API and can already do the aggregate join.

Indeed, the examples posted don't make much sense: thread/process
pools are the way to go.
History
Date User Action Args
2014-07-21 06:54:21neologixsetrecipients: + neologix, lemburg, tim.peters, aleax, rhettinger, pitrou, kristjan.jonsson, r.david.murray, Claudiu.Popa, Christian.Tismer, tinchester
2014-07-21 06:54:20neologixlinkissue22013 messages
2014-07-21 06:54:20neologixcreate