Author skrah
Recipients amaury.forgeotdarc, lemburg, mark.dickinson, skrah, vstinner
Date 2010-10-24.10:21:42
SpamBayes Score 1.46955e-12
Marked as misclassified No
Message-id <1287915705.68.0.697586370956.issue10156@psf.upfronthosting.co.za>
In-reply-to
Content
> 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.
History
Date User Action Args
2010-10-24 10:21:45skrahsetrecipients: + skrah, lemburg, amaury.forgeotdarc, mark.dickinson, vstinner
2010-10-24 10:21:45skrahsetmessageid: <1287915705.68.0.697586370956.issue10156@psf.upfronthosting.co.za>
2010-10-24 10:21:44skrahlinkissue10156 messages
2010-10-24 10:21:43skrahcreate