Stefan Krah <stefan-use...@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 down. ---------- Added file: http://bugs.python.org/file19351/unicode_init_globals2.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10156> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
