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 eric.snow
Recipients Arfrever, eric.snow, georg.brandl, ncoghlan, serhiy.storchaka, vstinner
Date 2013-11-08.00:27:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1383870432.77.0.206346500184.issue19518@psf.upfronthosting.co.za>
In-reply-to
Content
PEP 432 is all about the PyRun_* API and especially relates to refactoring it with the goal of improving extensibility and maintainability.  I'm sure Nick could expound, but the PEP is a response to the cruft that has accumulated over the years in Python/pythonrun.c.  The result of that organic growth makes it harder than necessary to do things like adding new commandline options.  While I haven't looked closely at the new function you added, I expect PEP 432 would have simplified things or even removed the need for a new function.
History
Date User Action Args
2013-11-08 00:27:12eric.snowsetrecipients: + eric.snow, georg.brandl, ncoghlan, vstinner, Arfrever, serhiy.storchaka
2013-11-08 00:27:12eric.snowsetmessageid: <1383870432.77.0.206346500184.issue19518@psf.upfronthosting.co.za>
2013-11-08 00:27:12eric.snowlinkissue19518 messages
2013-11-08 00:27:12eric.snowcreate