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 benjamin.peterson, jcea, meador.inge, ncoghlan, ron_adam, terry.reedy
Date 2011-12-21.03:10:58
SpamBayes Score 1.6114192e-05
Marked as misclassified No
Message-id <1324437059.67.0.996822497548.issue13607@psf.upfronthosting.co.za>
In-reply-to
Content
The thing that most appeals to me with this concept is moving closer to making it possible to experiment with generator-style functionality in *extension* modules (albeit extension modules that are coupled to private CPython APIs). So, for me, "not worse than the status quo" would be the main thing I'd be looking for out of any micro-benchmarks.

However, that also makes me question the movement of the "why_exit" from the frame to the tstate - having it on the thread state is significantly less flexible when it comes to experimenting with execution models.

The move from orthogonal bit flags in a dedicated enum to int fields and macro definitions also seems like a completely unnecessary pessimisation.
History
Date User Action Args
2011-12-21 03:10:59ncoghlansetrecipients: + ncoghlan, terry.reedy, jcea, ron_adam, benjamin.peterson, meador.inge
2011-12-21 03:10:59ncoghlansetmessageid: <1324437059.67.0.996822497548.issue13607@psf.upfronthosting.co.za>
2011-12-21 03:10:59ncoghlanlinkissue13607 messages
2011-12-21 03:10:58ncoghlancreate