On 20/01/2018 11:55, Thomas Jollans wrote:
> control is returned to t.resume. nonblocking_accept is supposed to be a
> coroutine
> Ergo, it schedules the nonblocking_accept coroutine (‘value’) to be
> called on the next iteration, and keeps the running listen_on coroutine
> (‘coroutine’) on the sta
On 19/01/18 22:50, Léo El Amri wrote:
> Hello list,
>
> I am currently trying to learn co-routine/asynchronous mechanisms in
> Python. I read the PEP 342, but I stumble on the fourth example.
> I don't understand what the lines "data = yield nonblocking_read(sock)"
> in echo_handler() and "connect
Hello list,
I am currently trying to learn co-routine/asynchronous mechanisms in
Python. I read the PEP 342, but I stumble on the fourth example.
I don't understand what the lines "data = yield nonblocking_read(sock)"
in echo_handler() and "connected_socket = yield
nonblocking_accept(sock)" in lis
