> The executor needs to know when no more futures will be scheduled so
> it can shutdown its thread/process pool after it has finished the
> current work items.
Ah, I see and it's useful indeed.
I think it makes things a bit counter-intuitive however. People are used
to "with" releasing thing
On 8 Nov 2009, at 03:13, Antoine Pitrou wrote:
The PEP is right here:
http://code.google.com/p/pythonfutures/source/browse/trunk/PEP.txt
I'm interested in hearing specific complaints about the API in the
context of what it's trying to *do*. The only thing which jumped out
at me was the numb
> The PEP is right here:
>
> http://code.google.com/p/pythonfutures/source/browse/trunk/PEP.txt
>
> I'm interested in hearing specific complaints about the API in the
> context of what it's trying to *do*. The only thing which jumped out
> at me was the number of methods on FutureList;
Yes that
