[Python-Dev] PEP 3148 ready for pronouncement (original) (raw)

Brian Quinlan brian at sweetapp.com
Thu May 27 08:20:04 CEST 2010

On May 27, 2010, at 1:21 PM, Greg Ewing wrote:

On 27/05/10 12:04, Jesse Noller wrote:

Namespaces are only a honking great idea if you actually let them do the job they're designed for. concurrent.* is the namespace, futures is the package within the namespace - concurrent.futures is highly descriptive of the items contained therein. I was referring to the issue of ThreadPool vs. ThreadPoolExecutor etc. By your own argument above, concurrent.futures.ThreadPool is quite descriptive enough of what it provides. It's not a problem if some other module also provides something called a ThreadPool.

I think that the "Executor" suffix is a good indicator of the
interface being provided. "Pool" is not because you can could have
Executor implementations that don't involve pools.

Cheers, Brian

More information about the Python-Dev mailing list