bpo-40170: Always define PyExceptionClass_Name as a function#24553
bpo-40170: Always define PyExceptionClass_Name as a function#24553vstinner merged 2 commits intopython:masterfrom
Conversation
Right, these changes impact the C API. If these changes were made after the latest Python 3.10 release, you can move the NEWS entries in a new PR. Otherwise, we can leave them, it's not a big deal. |
|
Merged, thanks. The function is only used to display errors, so I don't think that we need to micro-optimize the code (add an internal static inline function, for example), it's not "hot code". I consider that error handling is "cold code". |
All right. I prefer to move them before the next alpha. I'll throw up a PR. Thanks for reviewing 🙏🏻 |
…nGH-24553) Remove macro variant of PyExceptionClass_Name().
Remove the macro variant, as it accessed
PyTypeObject.tp_namedirectly.https://bugs.python.org/issue40170