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 ncoghlan, syncosmic, yselivanov
Date 2017-08-19.16:47:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1503161264.05.0.64731281301.issue31230@psf.upfronthosting.co.za>
In-reply-to
Content
> I started a local PR at https://github.com/ncoghlan/cpython/pull/1/files to explore what this might look like in practice.

Looks good to me.


> I'm less sure about __delegated_to__/__returns_to__, since we don't have *any* code in the standard library that reads gi_yieldfrom, and the only code that reads cr_await is a Python 3.5 compatibility hack in asyncio.

I'm -1 on this too.  gi_yieldfrom and cr_await are very special and rarely used things.  Refactoring or unifying them isn't trivial and ultimately not as useful.
History
Date User Action Args
2017-08-19 16:47:44yselivanovsetrecipients: + yselivanov, ncoghlan, syncosmic
2017-08-19 16:47:44yselivanovsetmessageid: <1503161264.05.0.64731281301.issue31230@psf.upfronthosting.co.za>
2017-08-19 16:47:44yselivanovlinkissue31230 messages
2017-08-19 16:47:43yselivanovcreate