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 Mark.Shannon, amaury.forgeotdarc, benjamin.peterson, ncoghlan, ron_adam
Date 2012-01-29.02:00:23
SpamBayes Score 3.1480107e-10
Marked as misclassified No
Message-id <>
The division of responsibilities between generator objects and the eval loop is currently a little messy. The eval loop deals almost entirely with frame objects and also handles swapping exception states around on behalf of generators, which is why the generator specific exception state currently lives on frame objects (i.e. to avoid the eval loop needing to know too much about the internal structure of generator objects).

Before generator related state can reasonably be moved out of the frame objects, those responsibilities should be divided more cleanly. Ron Adam has made an initially attempt at tackling that problem in issue 13607.

Once the responsibilities are divided appropriately, *then* we can look at the fields that ceval no longer touches and see if they should be moved somewhere else (whether that's directly into the generator struct or into a new struct referenced from the generator struct).
Date User Action Args
2012-01-29 02:00:26ncoghlansetrecipients: + ncoghlan, amaury.forgeotdarc, ron_adam, benjamin.peterson, Mark.Shannon
2012-01-29 02:00:25ncoghlansetmessageid: <>
2012-01-29 02:00:25ncoghlanlinkissue13897 messages
2012-01-29 02:00:23ncoghlancreate