Message119356
| Author |
skrah |
| Recipients |
amaury.forgeotdarc, lemburg, mark.dickinson, skrah, vstinner |
| Date |
2010年10月22日.00:03:30 |
| SpamBayes Score |
1.5585812e-08 |
| Marked as misclassified |
No |
| Message-id |
<1287705812.96.0.350985343924.issue10156@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Re disabling interning in PyDict_SetItemString:
A comment in unicodeobject.c says that globals should not be used
before calling _PyUnicode_Init. But in Py_InitializeEx (pythonrun.c)
_PyUnicode_Init is called after _Py_ReadyTypes, _PyFrame_Init,
_PyLong_Init, PyByteArray_Init and _PyFloat_Init.
In fact, when I move _PyUnicode_Init up, the error concerning
_PyFloat_Init disappears.
Problem is, PyType_Ready also uses PyDict_SetItemString, but I
presume that _Py_ReadyTypes has to be called before anything else.
In that case it would be unavoidable that PyDict_SetItemString is
used before _PyUnicode_Init, and it might be a good idea to disable
interning. |
|