Follow the discussion at#131799 (comment).

Currently, the Windows-related C code is mixed using the Python-specificPy_DEBUG macro and non-Python-specific_DEBUG macro.

The documentation said_DEBUG impliesPy_DEBUG.

Py_DEBUG

Compiling the interpreter with thePy_DEBUG macro defined produces what is generally meant bya debug build of Python. Py_DEBUG is enabled in the Unix build by adding--with-pydebug to the./configure command. It is also implied by the presence of the not-Python-specific_DEBUG macro. WhenPy_DEBUG is enabled in the Unix build, compiler optimization is disabled.

And it is guaranteed by the following code on Windows.

All platform-non-specific code and Unix-specific code is using the Python-specificPy_DEBUG macro. It would be nice to usePy_DEBUG in Windows-related C code either. It could improve the code readability and maintainability.

Linked PRs

• gh-131942: Use the Python-specificPy_DEBUG macro rather than_DEBUG in Windows-related C code #131944