Message 245664 - Python tracker

➜

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.

In-reply-to
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	<1435032749.45.0.137271412886.issue24450@psf.upfronthosting.co.za>

Content
Guido indicated on python-dev that he considered it reasonable to view adding gi_yieldfrom as part of the PEP 492 implementation: https://mail.python.org/pipermail/python-dev/2015-June/140498.html 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.

Content

Guido indicated on python-dev that he considered it reasonable to view adding gi_yieldfrom as part of the PEP 492 implementation: https://mail.python.org/pipermail/python-dev/2015-June/140498.html
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.

History
Date	User	Action	Args
2015年06月23日 04:12:29	ncoghlan	set	recipients: + ncoghlan, arigo, scoder, larry, fwierzbicki, ethan.furman, martin.panter, yselivanov, bennoleslie
2015年06月23日 04:12:29	ncoghlan	set	messageid: <1435032749.45.0.137271412886.issue24450@psf.upfronthosting.co.za>
2015年06月23日 04:12:29	ncoghlan	link	issue24450 messages
2015年06月23日 04:12:28	ncoghlan	create

homepage