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, Drekin, Gregory.Salvan, barry, dstufft, jcea, ncoghlan, sbspider, terry.reedy, twouters
Date 2016-06-05.01:03:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1465088590.36.0.601182332458.issue22257@psf.upfronthosting.co.za>
In-reply-to
Content
Looking at the potential impact of being able to use C99 initializers for the main configuration structs, I realised those could be a *lot* easier to work with if they consisted entirely of pointers to Python objects:

* NULL initialisation would correctly indicate "not set" for each value
* Running Py_XDECREF on every field will correctly release memory
* Boolean toggles are clearly separated from multi-value integers (PyBool vs PyLong)
* No conversion is needed to provide a read-only view of the config data at the Python level

This wouldn't be feasible for CoreConfig (since that is populated before Python object creation is permitted), but should work for MainInterpreterConfig and InterpreterConfig.
History
Date User Action Args
2016-06-05 01:03:10ncoghlansetrecipients: + ncoghlan, twouters, barry, terry.reedy, jcea, Arfrever, Drekin, dstufft, Gregory.Salvan, sbspider
2016-06-05 01:03:10ncoghlansetmessageid: <1465088590.36.0.601182332458.issue22257@psf.upfronthosting.co.za>
2016-06-05 01:03:10ncoghlanlinkissue22257 messages
2016-06-05 01:03:09ncoghlancreate