2012/12/21 Guido van Rossum :
> On Fri, Dec 21, 2012 at 1:00 PM, Antoine Pitrou wrote:
>> On Fri, 21 Dec 2012 12:37:25 -0800
>> Guido van Rossum wrote:
>>> I really meant *synchronously*... I usually start with working sync code
>>> and then figure out what to do to make it async. I'll give what
On Fri, Dec 21, 2012 at 1:00 PM, Antoine Pitrou wrote:
> On Fri, 21 Dec 2012 12:37:25 -0800
> Guido van Rossum wrote:
>> I really meant *synchronously*... I usually start with working sync code
>> and then figure out what to do to make it async. I'll give what you suggest
>> a try.
>
> Ah. Then I
On Fri, 21 Dec 2012 12:37:25 -0800
Guido van Rossum wrote:
> I really meant *synchronously*... I usually start with working sync code
> and then figure out what to do to make it async. I'll give what you suggest
> a try.
Ah. Then I hope the doc example can help you:
http://docs.python.org/dev/lib
I really meant *synchronously*... I usually start with working sync code
and then figure out what to do to make it async. I'll give what you suggest
a try.
--Guido van Rossum (sent from Android phone)
On Dec 21, 2012 11:54 AM, "Antoine Pitrou" wrote:
> On Fri, 21 Dec 2012 20:34:18 +0100 (CET)
>
On Fri, 21 Dec 2012 20:34:18 +0100 (CET)
guido.van.rossum wrote:
>
> - In either case, once it has a socket, it will wrap it in a
> - transport, and then enter a loop accepting connections (the best way
> - to implement such a loop depends on the platform). Each time a
> - connection is acc
