RetroSearch Browse

Thu Apr 23 18:13:14 CEST 2015 · https://mail.python.org/pipermail/python-dev/2015-April/139460.html

On 2015-04-23 11:26 AM, Victor Stinner wrote:
> 2015-04-23 17:22 GMT+02:00  <andrew.svetlov at gmail.com>:
>> I can live with `cocall fut()` but the difference between `data = yield from
>> loop.sock_recv(sock, 1024)` and `data = cocall (loop.sock_recv(sock,
>> 1024))()` frustrates me very much.
> You didn't answer to my question. My question is: is it possible to
> implement Future.__cocall__() since yield is defined in cofunctions.
> If it's possible, can you please show how? (Show me the code!)

I can do that.

class Future:
     ....
     def __iter__(self):
        ....
     __cocall__ = __iter__

I've outlined the problem with this approach in parallel
email: https://mail.python.org/pipermail/python-dev/2015-April/139456.html

Yury

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2015-April/139460.html below:

[Python-Dev] PEP 3152 and yield from Future()