René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Use the Python-specific `Py_DEBUG` macro rather than `_DEBUG` in Windows-related C code","articleBody":"Follow the discussion at https://github.com/python/cpython/pull/131799#discussion_r2021223342.\n\nCurrently, the Windows-related C code is mixed using the Python-specific `Py_DEBUG` macro and non-Python-specific `_DEBUG` macro.\n\nThe documentation said `_DEBUG` implies `Py_DEBUG`.\n\n\u003e ### [Py_DEBUG](https://docs.python.org/3/c-api/intro.html#c.Py_DEBUG)\n\u003e \n\u003e Compiling the interpreter with the `Py_DEBUG` macro defined produces what is generally meant by [a debug build of Python](https://docs.python.org/3/using/configure.html#debug-build). Py_DEBUG is enabled in the Unix build by adding [--with-pydebug](https://docs.python.org/3/using/configure.html#cmdoption-with-pydebug) to the `./configure` command. It is also implied by the presence of the not-Python-specific `_DEBUG` macro. When `Py_DEBUG` is enabled in the Unix build, compiler optimization is disabled.\n\nAnd it is guaranteed by the following code on Windows.\n\nhttps://github.com/python/cpython/blob/4940d96135a92b90bbc1dcc399f665817f956640/PC/pyconfig.h.in#L379-L381\n\nAll platform-non-specific code and Unix-specific code is using the Python-specific `Py_DEBUG` macro. It would be nice to use `Py_DEBUG` in Windows-related C code either. It could improve the code readability and maintainability.\n\n\u003c!-- gh-linked-prs --\u003e\n### Linked PRs\n* gh-131944\n\u003c!-- /gh-linked-prs --\u003e\n","author":{"url":"https://github.com/XuehaiPan","@type":"Person","name":"XuehaiPan"},"datePublished":"2025-03-31T15:24:13.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/131942/cpython/issues/131942"}