[issue10156] Initialization of globals in unicodeobject.c
report at bugs.python.org
Sun Oct 24 12:21:45 CEST 2010
Stefan Krah <stefan-usenet at bytereef.org> added the comment:
> why should _PyUnicode_Init() try to call _PyUnicode_InitGlobals() again?
For the embedding scenario (when only Py_Initialize() is called) I wanted
to preserve the old behavior of _PyUnicode_Init().
But this is not really enough. I wrote a new patch that also calls
_PyUnicode_InitGlobals() at the beginning of Py_Initialize().
I don't like the fact that even more clutter is added to Py_Main(). Perhaps
Py_Initialize() could be moved up or the Unicode functions could be moved
Added file: http://bugs.python.org/file19351/unicode_init_globals2.patch
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list