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 corona10, eric.snow, erlendaasland, kumaraditya, lazka, serhiy.storchaka, vstinner
Date 2022-02-16.19:26:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>

> Should we create the separate bpo issue if module changes are too noisy?

I think it's fine to use the one issue.  There are only 26 modules with `NEEDS_PY_IDENTIFIER` and none have much risk with the change.  So it's unlikely that we'll get any discussion about any specific module.  If we do, we can easily create an issue then for the module in question.  If one of the modules had many uses of `_Py_IDENTIFIER()` then it might make sense to split it out, but IIRC none of them have very many.
Date User Action Args
2022-02-16 19:26:45eric.snowsetrecipients: + eric.snow, vstinner, serhiy.storchaka, lazka, corona10, erlendaasland, kumaraditya
2022-02-16 19:26:45eric.snowsetmessageid: <>
2022-02-16 19:26:45eric.snowlinkissue46541 messages
2022-02-16 19:26:45eric.snowcreate