➜

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 Arfrever, eric.snow, georg.brandl, ncoghlan, serhiy.storchaka, vstinner
Date 2013-11-08.09:45:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7d29VMbRrAwusg093Cq+5eXXvE+QZ-kg1X3UR8_doZJfA@mail.gmail.com>
In-reply-to <1383870432.77.0.206346500184.issue19518@psf.upfronthosting.co.za>
Content 
PEP 432 doesn't really touch the PyRun_* APIs - it's all about refactoring
Py_Initialize so you can use most of the C API during the latter parts of
the configuration process (e.g. setting up the path for the import system).

pythonrun.c is just a monstrous beast that covers the entire interpreter
lifecycle from initialisation through script execution through to
termination.
History
Date User Action Args
2013-11-08 09:45:35ncoghlansetrecipients: + ncoghlan, georg.brandl, vstinner, Arfrever, eric.snow, serhiy.storchaka
2013-11-08 09:45:35ncoghlanlinkissue19518 messages
2013-11-08 09:45:35ncoghlancreate