René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"METH_* and Py_TPFLAGS* constants are documented as Python data","articleBody":"For example, a [search for Py_TPFLAGS](https://docs.python.org/3/search.html?q=Py_TPFLAGS) says it's all “Python data”:\r\n\u003e ![image](https://user-images.githubusercontent.com/302922/191553284-fef636e4-e2ef-471c-aca7-d45446e83be7.png)\r\n\r\nSame with [METH_](https://docs.python.org/3/search.html?q=METH_).\r\n\r\nI guess this should be changed to `c:macro:`. It doesn't change URLs, but it *would* break references and Intersphinx links in third-party docs.\r\nAnd there's a lot of references to these items that use `:const:` rather than `:c:macro:`. All of them would need to change, possibly causing conflicts in backports.\r\n\r\n---\r\n\r\nAn additional issue is flag combinations in [structures.rst](https://github.com/python/cpython/blob/3.11/Doc/c-api/structures.rst):\r\n\r\n```rest\r\n\r\n.. data:: METH_VARARGS\r\n\r\n   This is the typical calling convention, where[...]\r\n\r\n\r\n.. data:: METH_VARARGS | METH_KEYWORDS\r\n\r\n   Methods with these flags must [...]\r\n```\r\n\r\n---\r\n\r\nThese should look like items of the same category to the reader, but one is a valid `c:macro` and the other isn't.\r\n\r\n\r\nSphinx experts, any tips on how (and whether) to best fix this?\r\n","author":{"url":"https://github.com/encukou","@type":"Person","name":"encukou"},"datePublished":"2022-09-21T16:04:58.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":7},"url":"https://github.com/96996/cpython/issues/96996"}