Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions Doc/conf.py
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,7 @@
'sphinx.ext.coverage',
'sphinx.ext.doctest',
'sphinx.ext.extlinks',
'sphinx.ext.intersphinx',
]

# Skip if downstream redistributors haven't installed them
Expand Down Expand Up @@ -67,6 +68,12 @@

manpages_url = 'https://manpages.debian.org/{path}'

# Intersphinx configuration
intersphinx_mapping = {
'typing': ('https://typing.python.org/en/latest/', None),
}
intersphinx_disabled_reftypes = []

# General substitutions.
project = 'Python'
copyright = "2001 Python Software Foundation"
Expand Down
10 changes: 5 additions & 5 deletions Doc/library/typing.rst
Original file line number Diff line number Diff line change
Expand Up @@ -1650,7 +1650,8 @@ These can be used as types in annotations. They all support subscription using
# and `year` of type `int`.
def foo(**kwargs: Unpack[Movie]): ...

See :pep:`692` for more details on using ``Unpack`` for ``**kwargs`` typing.
See :ref:`the typing spec <typing:unpack-kwargs>` for more details on using
``Unpack`` for ``**kwargs`` typing.

.. versionadded:: 3.11

Expand Down Expand Up @@ -1766,7 +1767,7 @@ without the dedicated syntax, as documented below.
Manually created type variables may be explicitly marked covariant or contravariant by passing
``covariant=True`` or ``contravariant=True``.
By default, manually created type variables are invariant.
See :pep:`484` and :pep:`695` for more details.
See :ref:`the typing spec <typing:variance>` for more details.

Bounded type variables and constrained type variables have different
semantics in several important ways. Using a *bounded* type variable means
Expand Down Expand Up @@ -2008,7 +2009,7 @@ without the dedicated syntax, as documented below.
to ``call_soon`` match the types of the (positional) arguments of
``callback``.

See :pep:`646` for more details on type variable tuples.
See :ref:`the typing spec <typing:typevartuple>` for more details on type variable tuples.

.. attribute:: __name__

Expand Down Expand Up @@ -2168,8 +2169,7 @@ without the dedicated syntax, as documented below.
be pickled.

.. seealso::
* :pep:`612` -- Parameter Specification Variables (the PEP which introduced
``ParamSpec`` and ``Concatenate``)
* :ref:`typing:paramspec` -- typing specification for ``ParamSpec``
* :data:`Concatenate`
* :ref:`annotating-callables`

Expand Down
Loading