This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author yselivanov
Recipients Mark.Shannon, lukasz.langa, scoder, serhiy.storchaka, v2m, yselivanov
Date 2020-09-16.18:27:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1600280861.59.0.291569523631.issue41756@roundup.psfhosted.org>
In-reply-to
Content
> Since coroutines inherit the generator protocol more or less, I think "PyGen_Send()" is a more suitable name, better than "PyCoro_Send()".

OK, +1. PyGen_Send it is.

> Also should it be specific to generators/coroutines and accept PyGenObject*

I think it should be specific to generators and coroutines. Calling `PyObject_CallMethodIdOneArg(coro, &PyId_send, arg);` and interpreting exceptions to emulate the low level API seems a bit too much.
History
Date User Action Args
2020-09-16 18:27:41yselivanovsetrecipients: + yselivanov, scoder, lukasz.langa, Mark.Shannon, serhiy.storchaka, v2m
2020-09-16 18:27:41yselivanovsetmessageid: <1600280861.59.0.291569523631.issue41756@roundup.psfhosted.org>
2020-09-16 18:27:41yselivanovlinkissue41756 messages
2020-09-16 18:27:41yselivanovcreate