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 petr.viktorin
Recipients eric.snow, ncoghlan, petr.viktorin, shihai1991, vstinner
Date 2020-01-30.11:53:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> What is the problem between _Py_IDENTIFIER and multi-phase initialisation modules?

AFAIK there is no problem now, except possibly a race condition when initializing the identifiers.
It seems it's too easy to conflate porting to multi-phase initialization and getting rid of static state.

The problem will come with per-interpreter reference counting, or when the `str` class is no longer shared across all interpreters. For that, we'll need either per-interpreter identifiers, or solve the issue in another way.
Date User Action Args
2020-01-30 11:53:21petr.viktorinsetrecipients: + petr.viktorin, ncoghlan, vstinner, eric.snow, shihai1991
2020-01-30 11:53:21petr.viktorinsetmessageid: <>
2020-01-30 11:53:21petr.viktorinlinkissue39465 messages
2020-01-30 11:53:20petr.viktorincreate