[Python-Dev] PEP 3148 ready for pronouncement [ACCEPTED]

[Jesse Noller]

On Sun, Jul 11, 2010 at 10:07 PM, Benjamin Peterson <benjamin at python.org> wrote:
> 2010/7/11 Jesse Noller <jnoller at gmail.com>:
>> On Sat, May 22, 2010 at 11:38 AM, Guido van Rossum <guido at python.org> wrote:
>> [snip]
>>> Great points Jesse! Since I really don't have the time or expertise to
>>> make a judgment on this PEP, I hereby appoint you chair of the
>>> approval process for this PEP. That basically means that when you
>>> think it's ready to be approved, you say so, and it's a done deal. The
>>> remaining feedback cycle is up to you now -- it sounds like you're
>>> ready for closure, which sounds good to me (again, without having read
>>> the PEP or tried to write something using the proposed code). You can
>>> do it however you like: you can declare it approved now, or read it
>>> over once more yourself and suggest some final changes, or set a
>>> period (e.g. 48 hours) during which final comments have to be
>>> received, which you then will judge by merit or by your whim, or you
>>> can flip a coin or say a prayer... (I've tried most of those myself in
>>> the past and haven't done too badly if I say so myself. :-) You're the
>>> boss now. I know you will do the right thing for this PEP.
>>>
>>> --
>>> --Guido van Rossum (python.org/~guido)
>>>
>>
>> So, after some cool down - and the last rounds of discussion which
>> triggered some jiggery-pokery on Brian's part, I'm accepting PEP 3148
>> "futures - execute computations asynchronously". I feel that it's a
>> good addition, and a good start for something bigger down the road.
>>
>> Brian - you'll need to provide someone such as Martin or Georg your
>> public key for ssh access into SVN, and you'll need developer access
>> to the bug tracker.
>
> Oh, don't worry. He's already been hacking happily on Windows stuff.
>
>
> --
> Regards,
> Benjamin
>

Wrong Brian - that's Brian Curtin, this is Brian Quinlan - I double
checked the committer's list (http://www.python.org/dev/committers).

We now have two Brians. I say we name them PresentBrian and FutureBrian.

jesse