Message119503
> 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. |
|
Date |
User |
Action |
Args |
2010-10-24 10:21:45 | skrah | set | recipients:
+ skrah, lemburg, amaury.forgeotdarc, mark.dickinson, vstinner |
2010-10-24 10:21:45 | skrah | set | messageid: <1287915705.68.0.697586370956.issue10156@psf.upfronthosting.co.za> |
2010-10-24 10:21:44 | skrah | link | issue10156 messages |
2010-10-24 10:21:43 | skrah | create | |
|