STINNER Victor <vstin...@python.org> added the comment:
> Both https://github.com/python/cpython/pull/18066 (collections module) and > https://github.com/python/cpython/pull/18032 (asyncio module) ran into the > problem where porting them to multi-phase initialisation involves replacing > their usage of the `_Py_IDENTIFIER` macro with some other mechanism. What is the problem between _Py_IDENTIFIER and multi-phase initialisation modules? If both are incompatible, we may need a different but similar API: values would be stored in a hash table per module object. The hash table can be stored in the module object directly, or it can be store in a second hash table (module => hash table). If we want a unified API, maybe we can use module=NULL (or any other marker) for "global" identifiers (not specific to a module). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue39465> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
