On Sat, Jan 16, 2010 at 5:22 PM, Brian Quinlan <br...@sweetapp.com> wrote:

> It is definitely true that you can roll your own implementation using
> threads but the purpose of the futures library is to make that unnecessary.

I'd like to stress this; futures/pools/etc are common enough patterns
(and I get requests to add more to multiprocessing) that it makes
sense as an add-on to the stdlib. This is sugar; not magic.

jesse
_______________________________________________
stdlib-sig mailing list
stdlib-sig@python.org
http://mail.python.org/mailman/listinfo/stdlib-sig

Reply via email to