On 21 November 2017 at 01:31, Eric Snow <ericsnowcurren...@gmail.com> wrote: > On Nov 18, 2017 19:20, "Nick Coghlan" <ncogh...@gmail.com> wrote: > > > OK, in that case I think the answer to Victor's question is: > > 1. Breaking calling Py_DecodeLocale() before calling Py_Initialize() > 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, Py_DecodeLocale() > should be the only "Process-wide parameter" needing repair. I suppose, > PyMem_RawMalloc() and PyMem_RawFree() *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 | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com