Idea: link builtin types and exceptions to their resp. docs about pytkdocs

[StephenBrown2]

Sphinx does this with it's own magic, but has an extension to link to other project's documentation called "intersphinx": http://www.sphinx-doc.org/en/master/usage/extensions/intersphinx.html
This relies on an "inventory" mapping file being available, and so may not be the exact thing you're looking for, but the example to view the links is here.

Here is an example configuration cribbed from another project I worked on that used Sphinx for docs:

# Example configuration for intersphinx: refer to the Python standard library.
intersphinx_mapping = {
    'python': ('https://docs.python.org/3', None),
    'cryptography': ('https://cryptography.io/en/latest', None),
}

[pawamoy]

This is definitely interesting. I feel like I'm trying to reinvent the wheel haha.

I was indeed thinking that instead of maintaining a global mapping, each project could serve its own mapping file. We would just need to retrieve the doc page for each project, then their mapping files, and use that to create cross references.

[pawamoy]

Partially implemented in mkdocstrings, which is now able to load and use Sphinx inventories to reference external objects. The new griffe collector will return objects' API paths so mkdocstrings can add further references.