This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author shihai1991
Recipients Jim Fasarakis-Hilliard, amaury.forgeotdarc, corona10, eric.snow, isoschiz, koubaa, kylotan, lukasz.langa, miss-islington, pconnell, phsilva, python-dev, santoso.wijaya, shihai1991, tlesher, vstinner, ysj.ray
Date 2020-08-13.04:46:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Py_Finalize() calls _PyUnicode_ClearInterned() which clears interned strings. Which strings are still alive after Py_Finalize()?

Yes.especially those encodings, interpreter leaks much encodings refcount after Py_Finalize(). I am not sure they are corner cases or not.
Maybe we could check it again afer we have done all convert works.

No matter how many times `Py_Initialize(); Py_Finalize();` have called, Holding a same interned of unicodeobject.c all the time sound like a stupied idea.
Date User Action Args
2020-08-13 04:46:06shihai1991setrecipients: + shihai1991, amaury.forgeotdarc, kylotan, vstinner, tlesher, phsilva, ysj.ray, santoso.wijaya, lukasz.langa, python-dev, eric.snow, pconnell, isoschiz, Jim Fasarakis-Hilliard, corona10, miss-islington, koubaa
2020-08-13 04:46:06shihai1991setmessageid: <>
2020-08-13 04:46:06shihai1991linkissue1635741 messages
2020-08-13 04:46:06shihai1991create