[Python-Dev] Python initialization and embedded Python (original) (raw)

Nick Coghlan ncoghlan at gmail.com
Mon Nov 20 21:24:44 EST 2017

On 21 November 2017 at 01:31, Eric Snow <ericsnowcurrently at gmail.com> wrote:

On Nov 18, 2017 19:20, "Nick Coghlan" <ncoghlan at gmail.com> wrote:

OK, in that case I think the answer to Victor's question is: 1. Breaking calling PyDecodeLocale() before calling PyInitialize() is a compatibility break with the API implied by our own usage examples, and we'll need to revert the breakage for 3.7, +1 The break was certainly unintentional. :/ Fortunately, PyDecodeLocale() should be the only "Process-wide parameter" needing repair. I suppose, PyMemRawMalloc() and PyMemRawFree() could be considered too, but my understanding is that they aren't really intended for direct use (especially pre-init).

PyMem_RawFree will need to continue working pre-initialize as well, since it's the specified cleanup function for Py_DecodeLocale.

Cheers, Nick.

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

More information about the Python-Dev mailing list