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 martin.panter, ncoghlan, njs, vstinner, yselivanov
Date 2016-11-14.12:16:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1479125783.11.0.560804320887.issue28629@psf.upfronthosting.co.za>
In-reply-to
Content
Oops, I forgot to mention one other potential cost-minimisation strategy for a `co_cleanuptab` field: only populate it with setup/cleanup opcode pairs that include a yield, yield from, or await operation between them. 

The potential benefit I can see to *not* doing that is that if the information is always available (even on synchronous frames), then greenlet based frameworks like gevent may be able to make use of it.
History
Date User Action Args
2016-11-14 12:16:23ncoghlansetrecipients: + ncoghlan, vstinner, njs, martin.panter, yselivanov
2016-11-14 12:16:23ncoghlansetmessageid: <1479125783.11.0.560804320887.issue28629@psf.upfronthosting.co.za>
2016-11-14 12:16:23ncoghlanlinkissue28629 messages
2016-11-14 12:16:22ncoghlancreate