I think changing const to data would fix this too. Looking at the python objects.invwith the sphobjinv package, True is definitely a linkable target:

DataObjStr(name='True', domain='py', role='data', priority='1', uri='library/constants.html#$', dispname='-')

Actually, :const:`True` should work just fine, the python docs do it: https://github.com/python/cpython/blob/323188360d61875bd68688ef41711bade298af50/Doc/library/decimal.rst#L610

I think it would be better to work out why these links do not work.

const:`True` in the python docs works because there's the document of True in the python docs (https://github.com/python/cpython/blob/323188360d61875bd68688ef41711bade298af50/Doc/library/constants.rst, https://docs.python.org/3/library/constants.html#True). In the numpy docs, I think external link can be used to point the document of True in the python docs.

I was under the impression that intersphinx would automatically follow the link. Does :const:`python:True` work instead? Or perhaps :py:const:`True` , if the issue is these files are not using python

:py:data:`True` seems to work correctly.

Does :py:const: work too?

No, :py:const: doesn't work.

It may be worth opening an issue against sphinx.

Tried to fix the doc CI, but realized that won't work as CircleCI is silly - you'll need to rebase.

Thanks @takanori-pskq

Yeah, intersphinx only knows how to wire cross-references together using the domain and role exactly as specified in the objects.inv.

Since True is present in the Python docs objects.inv as belonging to :py:data:, that's the only way you can successfully craft the reference.

As best I understand it, the :const: role is likely only ever going to work for cross-references made to targets within the same documentation set.