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 Decorater, eric.snow, ncoghlan, serhiy.storchaka, vstinner
Date 2017-11-23.00:04:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1511395482.65.0.213398074469.issue32096@psf.upfronthosting.co.za>
In-reply-to
Content
Victor, I think you're fundamentally misunderstanding the goals of PEP 432.

The entire point is to let people have a *mostly working Python runtime* during CPython startup. Moving everything that Py_Initialize needs to instead have to happen before Py_InitializeRuntime (aka _Py_CoreInitialize) defeats that point.

CoreConfig should thus contain *as little as possible*, with most of the environmental querying work moving into Py_ReadMainInterpreterConfig.

So could you please move everything you've added to CoreConfig (that isn't genuinely required to from the moment the runtime starts doing anything) out again, and either put it into the main interpreter config as Python objects (as described in PEP 432), or else into a new intermediate configuration struct?
History
Date User Action Args
2017-11-23 00:04:42ncoghlansetrecipients: + ncoghlan, vstinner, eric.snow, serhiy.storchaka, Decorater
2017-11-23 00:04:42ncoghlansetmessageid: <1511395482.65.0.213398074469.issue32096@psf.upfronthosting.co.za>
2017-11-23 00:04:42ncoghlanlinkissue32096 messages
2017-11-23 00:04:42ncoghlancreate