A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2010-May/100420.html below:

[Python-Dev] PEP 3148 ready for pronouncement

[Python-Dev] PEP 3148 ready for pronouncement [Python-Dev] PEP 3148 ready for pronouncementAntoine Pitrou solipsis at pitrou.net
Thu May 27 18:16:38 CEST 2010
On Fri, 28 May 2010 02:05:14 +1000
Nick Coghlan <ncoghlan at gmail.com> wrote:
> 
> Executors and thread pools are not the same thing.
> 
> I might create a thread pool for *anything*. An executor will always 
> have a specific execution model associated with it (whether it be called 
> futures, as in this case, or runnables or something else).

I'm sorry, but what is the specific execution model you are talking
about, and how is it different from what you usually do with a thread
pool?  Why would you do something other with a thread pool than running
tasks and (optionally) collecting their results?

Thanks

Antoine.


More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4