You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many of the C "constants" (actually macros without parameters) are declared in the documentation using the data directive and referred using :data: and :const: roles. It is incorrect, because these directive and roles are defined in the Python domain and purposed to use with Python module level variables. I think that it is better to document them as they are, the C macros.
One of the differences is that the HTML anchors contains the c. prefix, e.g. c.METH_VARARGS. There may also be the difference in visual representation.
Other issues in the current markup:
In the index they are marked as "(built-in variable)".
There are no index entries for METH_KEYWORDS and METH_METHOD and they cannot be referred.
There are two definitions of Py_TPFLAGS_HAVE_GC. They does not conflict only because they are in different namespaces.
Activity
[-]Use proper narjup for the C "constants"[/-][+]Use proper markup for the C "constants"[/+]pythongh-106919: Use role :c:macro: for referencing the C "constants"
gh-106919: Use role :c:macro: for referencing the C "constants" (GH-1…
[3.12] pythongh-106919: Use role :c:macro: for referencing the C "con…
[3.11] pythongh-106919: Use role :c:macro: for referencing the C "con…
[3.12] gh-106919: Use role :c:macro: for referencing the C "constants" (
[3.11] gh-106919: Use role :c:macro: for referencing the C "constants" (
encukou commentedon Aug 2, 2023
Are you aware of the discussion in #96996?