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 ncoghlan
Recipients Tilka, ncoghlan, sbt
Date 2013-05-22.08:15:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Actors are just as vulnerable to the "new threads/processes are expensive" issue as anything else, and by using a dynamic pool appropriately you can amortise those costs across multiple instances.

The point is to expose a less opinionated threading model in a more readily accessible way. Executors and futures are *very* opinionated about the communication channels you're expected to use (the ones the executor provides), while pools are just a resource management tool.
Date User Action Args
2013-05-22 08:15:10ncoghlansetrecipients: + ncoghlan, sbt, Tilka
2013-05-22 08:15:10ncoghlansetmessageid: <>
2013-05-22 08:15:10ncoghlanlinkissue17140 messages
2013-05-22 08:15:10ncoghlancreate