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 eric.snow
Recipients Mark.Shannon, corona10, craigh, diabonas, eric.snow, erlendaasland, hroncok, methane, ndjensen, pablogsal, serhiy.storchaka, vstinner
Date 2021-12-15.19:52:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1639597979.34.0.170973692095.issue46006@roundup.psfhosted.org>
In-reply-to
Content
FWIW, it makes sense to me for the interned strings to be per-interpreter eventually.
Otherwise strings interned by an interpreter would persist after that interpreter
is finalized, potentially leaking memory until the runtime is finalized.

However, if we end up with immortal objects then I think all the strings created
through _Py_IDENTIFIER() should be global (_PyRuntimeState).  Otherwise they must
be per-interpreter (if we have a per-interpreter GIL).
History
Date User Action Args
2021-12-15 19:52:59eric.snowsetrecipients: + eric.snow, vstinner, craigh, methane, Mark.Shannon, serhiy.storchaka, ndjensen, hroncok, corona10, pablogsal, erlendaasland, diabonas
2021-12-15 19:52:59eric.snowsetmessageid: <1639597979.34.0.170973692095.issue46006@roundup.psfhosted.org>
2021-12-15 19:52:59eric.snowlinkissue46006 messages
2021-12-15 19:52:59eric.snowcreate