Author vstinner
Recipients eric.snow, ncoghlan, vstinner
Date 2018-11-16.14:44:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1542379446.44.0.788709270274.issue35266@psf.upfronthosting.co.za>
In-reply-to
Content
The C code of Python initialization uses _PyCoreConfig and _PyMainInterpreterConfig which co-exist and more or less redundant. For example, both structures have "argv": wchar_** for _PyCoreConfig, PyObject* (list of str) for _PyMainInterpreterConfig.

I propose to put _PyCoreConfig inside _PyMainInterpreterConfig and move wchar_t* strings into a new _PyPreConfig structure.

The main idea is that _PyPreConfig and wchar_* type are only used for early Python initialization, but once Python is initialization, the configuration should be provided as Python objects.

I didn't check all configuration variables to see if it's doable or not, but I wrote a proof-of-concept pull request to show my idea with concrete (and working!) code.

See attached PR.
History
Date User Action Args
2018-11-16 14:44:06vstinnersetrecipients: + vstinner, ncoghlan, eric.snow
2018-11-16 14:44:06vstinnersetmessageid: <1542379446.44.0.788709270274.issue35266@psf.upfronthosting.co.za>
2018-11-16 14:44:06vstinnerlinkissue35266 messages
2018-11-16 14:44:06vstinnercreate