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 ncoghlan
Recipients ncoghlan, syncosmic, yselivanov
Date 2017-08-19.03:56:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I agree is orthogonal - refactoring the current logic is useful regardless of what we do at the object attribute layer.

Regarding __delegated_to__/__returns_to__, the reason I like *not* having "async" in the attribute names is that generators are actually used as a synchronous construct (via synchronous for loops and next() calls), even though they technically define an asynchronous operation from the interpreter's point of view.

The reason I like omitting "call" (or "calls") from the name is that even though "yield from" and "await" are both sometimes described as providing syntax for asynchronous calls, that terminology is really only defensible for "await" - PEP 380 describes the "yield from" operation as delegating to a subgenerator, and I think that's a better way of framing the general concept.
Date User Action Args
2017-08-19 03:56:58ncoghlansetrecipients: + ncoghlan, yselivanov, syncosmic
2017-08-19 03:56:58ncoghlansetmessageid: <>
2017-08-19 03:56:58ncoghlanlinkissue31230 messages
2017-08-19 03:56:57ncoghlancreate