➜

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 vstinner
Recipients eric.snow, kumaraditya, serhiy.storchaka, vstinner
Date 2022-01-28.11:16:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1643368597.45.0.18459311308.issue46541@roundup.psfhosted.org>
In-reply-to
Content 
> `_Py_Identifier` has been useful but at this point there is a faster and simpler approach we could take as a replacement: statically initialize the objects as fields on `_PyRuntimeState` and reference them directly through a macro.

This change is going to break projects in the wild. Yes, people use the _Py_IDENTIFIER(), _PyUnicode_FromId() and other "Id" variant of many functions in 3rd party projects.

Is it possible to keep runtime initialization if this API is used by 3rd party code?
History
Date User Action Args
2022-01-28 11:16:37vstinnersetrecipients: + vstinner, eric.snow, serhiy.storchaka, kumaraditya
2022-01-28 11:16:37vstinnersetmessageid: <1643368597.45.0.18459311308.issue46541@roundup.psfhosted.org>
2022-01-28 11:16:37vstinnerlinkissue46541 messages
2022-01-28 11:16:37vstinnercreate