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 ncoghlan
Date 2014-11-14.11:18:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1415963921.95.0.551930895546.issue22869@psf.upfronthosting.co.za>
In-reply-to
Content
When working on the original reference implementation for PEP 432, I found it useful to split the startup & shutdown code out from the main entry points into the eval loop (see issue 22257 for more details).

However, that split made the draft implementation rather hard to maintain - any CPython commit that touched pythonrun.c was almost certain to cause a merge conflict.

The attached patch is a preliminary split into two separate modules, with pythonrun continuing to hold the main eval loop entry points, while the startup and shutdown code moves into pylifecycle.

This is an initial WIP patch (that nonetheless passes the test suite). I started work on it a few months ago, so I need to make sure that I've retained Victor's recent pythonrun changes.
History
Date User Action Args
2014-11-14 11:18:42ncoghlansetrecipients: + ncoghlan
2014-11-14 11:18:41ncoghlansetmessageid: <1415963921.95.0.551930895546.issue22869@psf.upfronthosting.co.za>
2014-11-14 11:18:41ncoghlanlinkissue22869 messages
2014-11-14 11:18:41ncoghlancreate