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
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