--- El sáb, 11/12/10, Brian Quinlan escribió:
>
> On Dec 11, 2010, at 6:44 AM, Thomas Nagy wrote:
>
> > --- El vie, 10/12/10, Brian Quinlan escribió:
> >> On Dec 10, 2010, at 10:51 AM, Thomas Nagy wrote:
> >>> --- El vie, 10/12/10, Brian Quinlan
> escri
--- El vie, 10/12/10, Brian Quinlan escribió:
> On Dec 10, 2010, at 10:51 AM, Thomas Nagy wrote:
> > --- El vie, 10/12/10, Brian Quinlan escribió:
> >> On Dec 10, 2010, at 5:36 AM, Thomas Nagy wrote:
> >>> I have a process running for a long time, and
> which
--- El vie, 10/12/10, Thomas Nagy escribió:
> --- El vie, 10/12/10, Brian Quinlan
> escribió:
> > On Dec 10, 2010, at 5:36 AM, Thomas Nagy wrote:
> > > I have a process running for a long time, and
> which
> > may use futures of different max_workers count. I
> th
--- El vie, 10/12/10, Brian Quinlan escribió:
> On Dec 10, 2010, at 5:36 AM, Thomas Nagy wrote:
> > I have a process running for a long time, and which
> may use futures of different max_workers count. I think it
> is not too far-fetched to create a new futures object each
&
--- El jue, 9/12/10, Brian Quinlan escribió:
> On Dec 9, 2010, at 4:26 AM, Thomas Nagy wrote:
>
> > 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 py
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?
2.
