Sphinx Python Domain: :var: Fields Incorrectly Cross-Reference Variable Names

You are working in the sphinx-doc/sphinx repository at commit 4b452338f914d4f6b54704222d70ae8a746e3db5.

Problem

In Sphinx's Python domain, docstring field lists accept :var:, :ivar:, and :cvar: field types to document instance, class, and plain variables on a class or module. These fields accept an optional type annotation and a variable name, for example:

.. py:class:: MyClass

   :var int attr: Some integer attribute.

The bug: the variable name (attr in the example above) is currently wrapped in a pending_xref node — the same mechanism Sphinx uses to resolve cross-references to other objects in the documentation. This causes Sphinx to attempt a cross-reference lookup for the bare variable name attr, which can match unrelated attributes in other classes or modules. The variable name should be rendered as addnodes.literal_strong (plain bold monospace text), not as a hyperlink to wherever Sphinx can find something named attr.

The type annotation (int in the example) must continue to produce a pending_xref with reftype='class' so that type names resolve normally.

Requirements / Interface

1. File to modify: sphinx/domains/python.py

2. Target object: The PyTypedField instance named 'variable' (field names 'var', 'ivar', 'cvar') defined inside PyObject.doc_field_types. At the base commit this entry looks roughly like:

```python
PyTypedField('variable', label=_('Variables'),
names=('var', 'ivar', 'cvar'),
typerolename='class', rolename='obj',
can_collapse=True),
```

3. Required change: The rolename='obj' argument causes the field argument (variable name) to become a pending_xref. Remove or replace that argument so the variable name is emitted as addnodes.literal_strong instead. The typerolename='class' must be preserved so type annotations still cross-reference as class objects.

4. Test that must pass (added by the hidden test patch): tests/test_domain_py.py::test_info_field_list_var

The hidden test parses the RST:

```rst
.. py:class:: Class

:var int attr: blah blah
```

and asserts that the field list entry for attr is structured as:

```
(
[addnodes.literal_strong, 'attr'],
' (',
[pending_xref, addnodes.literal_emphasis, 'int'],
')',
' -- ',
'blah blah'
)
```

Crucially, attr must not be inside a pending_xref node.

5. All 34 pre-existing tests in tests/test_domain_py.py listed in the pass-to-pass set must continue to pass.

Examples

Before the fix (current behaviour)

Parsing :var int attr: blah blah inside a .. py:class:: directive produces a node tree that wraps the variable name in a cross-reference:

pending_xref(attr)   literal_emphasis(int)   text('blah blah')

Because pending_xref(attr) is resolved against the entire documentation tree, it can silently link attr to an unrelated class attribute that happens to share the name.

After the fix

literal_strong(attr)   pending_xref → literal_emphasis(int)   text('blah blah')

No cross-reference is produced for the variable name itself.

Constraints

• •Only modify sphinx/domains/python.py (and tests/test_domain_py.py if you want to add the test locally, but the hidden grader will apply its own test patch regardless).
• •Do not alter the typerolename='class' argument — type annotations must still resolve.
• •Do not change the field names 'var', 'ivar', 'cvar' or the can_collapse=True setting.
• •The rolename parameter in TypedField / PyTypedField controls whether the field argument gets a cross-reference. Setting it to an empty string or omitting it entirely is the idiomatic Sphinx fix.
• •The fix is a single-line or very small change. Large refactors of docfields.py or PyTypedField internals are out of scope and may break other tests.

Scoring

Your submission is accepted if:

1. The hidden test tests/test_domain_py.py::test_info_field_list_var passes.
2. All 34 pass-to-pass tests in tests/test_domain_py.py continue to pass.

Leaderboards additionally rank accepted runs by estimated token usage, cost, and wall-clock time.