[Python-Dev] New _Py_InitializeFromConfig() function (PEP 432)

Nick Coghlan ncoghlan at gmail.com
Sat Aug 4 03:57:36 EDT 2018

On 2 August 2018 at 19:49, Victor Stinner <vstinner at redhat.com> wrote:
> About that, I'm working on a subproject: abandon Py_xxx global
> configuration variables to replace them with accessing
> interpreter->core_config->xxx. I'm not sure yet if it's a good idea or
> not, but it would allow to have two interpreters to have their own
> different configuration. Imagine two interpreters with different
> sys.path running in isolated mode. Or maybe an interpreter without
> importlib?
> One of the issue is that we have now two copies of the same option.
> For example, Py_BytesWarningFlag and
> interpreter->core_config->bytes_warning. That's why I would like to
> switch to core_config.

One of the challenges we have around those is the backwards
compatibility implications for embedding applications, so I suspect
the earliest we'll be able to make that change is in the release after
the new initialisation API becomes public.


Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

More information about the Python-Dev mailing list