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 arigo, bennoleslie, ethan.furman, fwierzbicki, larry, martin.panter, ncoghlan, scoder, yselivanov
Date 2015-06-23.04:12:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Guido indicated on python-dev that he considered it reasonable to view adding gi_yieldfrom as part of the PEP 492 implementation:

That perspective makes sense to me as well, since it preserves the functional equivalence of native coroutines (cr_await) and generator based coroutines (gi_yieldfrom) from a state introspection perspective.

I've added Larry to the nosy list here to give him the option of veto'ing as release manager, but I think we want both in order to get full debuggability benefits.
Date User Action Args
2015-06-23 04:12:29ncoghlansetrecipients: + ncoghlan, arigo, scoder, larry, fwierzbicki, ethan.furman, martin.panter, yselivanov, bennoleslie
2015-06-23 04:12:29ncoghlansetmessageid: <>
2015-06-23 04:12:29ncoghlanlinkissue24450 messages
2015-06-23 04:12:28ncoghlancreate