[Python-Dev] New Python Initialization API (original) (raw)

Inada Naoki songofacandy at gmail.com
Sat Apr 6 01:09:37 EDT 2019

On Sat, Apr 6, 2019 at 1:13 AM Victor Stinner <vstinner at redhat.com> wrote:

> > PyPreConfig fields: > > > > * coerceclocalewarn: if non-zero, emit a warning if the C locale > > is coerced. > > * coerceclocale: if equals to 2, coerce the C locale; if equals to > > 1, read the LCCTYPE to decide if it should be coerced. > > Can we use another value for coerceclocale to determine whether to > warn or not? Save a field. coerceclocale is already complex, it can have 4 values: -1, 0, 1 and 2. I prefer keep a separated field. Moreover, I understood that you might want to coerce the C locale and get the warning, or get the warning but not coerce the locale.

Are these configurations are really needed?

Applications embedding Python may not initialize Python interpreter at first. For example, vim initializes Python when Python is used first time.

On the other hand, C locale coercion should be done ASAP application starts.

I think dedicated API for coercing C locale is better than preconfig.

// When application starts: Py_CoerceCLocale(warn=0);

// later... Py_Initialize();

-- Inada Naoki <songofacandy at gmail.com>

More information about the Python-Dev mailing list