On Thu, Dec 9, 2010 at 04:26, Thomas Nagy <tnagyemail-m...@yahoo.fr> wrote:
> Hello,
>
> I am looking forward to replacing a piece of code 
> (http://code.google.com/p/waf/source/browse/trunk/waflib/Runner.py#86) by the 
> futures module which was announced in python 3.2 beta. I am a bit stuck with 
> it, so I have a few questions about the futures:
>
> 1. Is the futures API frozen?

It will be once Python 3.2 final is released.

-Brett

> 2. How hard would it be to return the tasks processed in an output queue to 
> process/consume the results while they are returned? The code does not seem 
> to be very open for monkey patching.
> 3. How hard would it be to add new tasks dynamically (after a task is 
> executed) and have the futures object never complete?
> 4. Is there a performance evaluation of the futures code (execution overhead) 
> ?
>
> Thanks,
> Thomas
>
>
>
>
> _______________________________________________
> Python-Dev mailing list
> Python-Dev@python.org
> http://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: 
> http://mail.python.org/mailman/options/python-dev/brett%40python.org
>
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Reply via email to