[3.15] Doc: Fix documentation links that pointed to other objects (GH-160871)

(cherry picked from commit e8e7ffd)

Co-authored-by: Inada Naoki <songofacandy@gmail.com>

Author: methane

Doc/library/calendar.rst

@@ -432,7 +432,8 @@ For simple text calendars this module provides the following functions.
 
 .. function:: prcal(theyear, w=0, l=0, c=6, m=3)
 
-   Prints the calendar for an entire year as returned by  :func:`calendar`.
+   Prints the calendar for an entire year as returned by
+   :func:`~calendar.calendar`.
 
 
 .. function:: calendar(theyear, w=2, l=1, c=6, m=3)

Doc/library/datetime.rst

@@ -1386,9 +1386,9 @@ Instance methods:
    hour=self.hour, minute=self.minute, second=self.second, microsecond=self.microsecond, \
    tzinfo=self.tzinfo, *, fold=0)
 
-   Return a new :class:`datetime` object with the same attributes, but with
-   specified parameters updated. Note that ``tzinfo=None`` can be specified to
-   create a naive datetime from an aware datetime with no conversion of date
+   Return a new :class:`~datetime.datetime` object with the same attributes, but
+   with specified parameters updated. Note that ``tzinfo=None`` can be specified
+   to create a naive datetime from an aware datetime with no conversion of date
    and time data.
 
    :class:`.datetime` objects are also supported by generic function

Doc/library/dis.rst

@@ -375,7 +375,7 @@ operation is being performed, so the intermediate analysis object isn't useful:
    source line information (if any) is taken directly from the disassembled code
    object.
 
-   The *adaptive* parameter works as it does in :func:`dis`.
+   The *adaptive* parameter works as it does in :func:`~dis.dis`.
 
    .. versionadded:: 3.4
 

Doc/library/fnmatch.rst

@@ -53,7 +53,8 @@ a :class:`!str` filename, and vice-versa.
 
 Finally, note that :deco:`functools.lru_cache` with a *maxsize* of 32768
 is used to cache the (typed) compiled regex patterns in the following
-functions: :func:`fnmatch`, :func:`fnmatchcase`, :func:`.filter`, :func:`.filterfalse`.
+functions: :func:`~fnmatch.fnmatch`, :func:`fnmatchcase`, :func:`.filter`,
+:func:`.filterfalse`.
 
 
 .. function:: fnmatch(name, pat)

Doc/library/getopt.rst

@@ -80,10 +80,10 @@ exception:
 
 .. function:: gnu_getopt(args, shortopts, longopts=[])
 
-   This function works like :func:`getopt`, except that GNU style scanning mode is
-   used by default. This means that option and non-option arguments may be
-   intermixed. The :func:`getopt` function stops processing options as soon as a
-   non-option argument is encountered.
+   This function works like :func:`~getopt.getopt`, except that GNU style
+   scanning mode is used by default. This means that option and non-option
+   arguments may be intermixed. The :func:`~getopt.getopt` function stops
+   processing options as soon as a non-option argument is encountered.
 
    If the first character of the option string is ``'+'``, or if the environment
    variable :envvar:`!POSIXLY_CORRECT` is set, then option processing stops as

Doc/library/getpass.rst

@@ -27,13 +27,14 @@ The :mod:`!getpass` module provides two functions:
    typed character is replaced by it. For example, ``echo_char='*'`` will
    display asterisks instead of the actual input.
 
-   If echo free input is unavailable getpass() falls back to printing
-   a warning message to *stream* and reading from ``sys.stdin`` and
+   If echo-free input is unavailable, :func:`~getpass.getpass` falls back to
+   printing a warning message to *stream* and reading from :data:`sys.stdin` and
    issuing a :exc:`GetPassWarning`.
 
    .. note::
-      If you call getpass from within IDLE, the input may be done in the
-      terminal you launched IDLE from rather than the idle window itself.
+      If you call :func:`~getpass.getpass` from within IDLE, the input may be
+      done in the terminal you launched IDLE from rather than the idle window
+      itself.
 
    .. note::
       On Unix systems, when *echo_char* is set, the terminal will be

Doc/library/gettext.rst

@@ -89,8 +89,9 @@ class-based API instead.
 .. function:: dnpgettext(domain, context, singular, plural, n, /)
 
    Similar to the corresponding functions without the ``p`` in the prefix (that
-   is, :func:`gettext`, :func:`dgettext`, :func:`ngettext`, :func:`dngettext`),
-   but the translation is restricted to the given message *context*.
+   is, :func:`~gettext.gettext`, :func:`dgettext`, :func:`ngettext`,
+   :func:`dngettext`), but the translation is restricted to the given message
+   *context*.
 
    .. versionadded:: 3.8
 
@@ -426,7 +427,8 @@ take the following steps:
 
 In order to prepare your code for I18N, you need to look at all the strings in
 your files.  Any string that needs to be translated should be marked by wrapping
-it in ``_('...')`` --- that is, a call to the function :func:`_ <gettext>`.  For example::
+it in ``_('...')`` --- that is, a call to the function
+:func:`_ <gettext.gettext>`.  For example::
 
    filename = 'mylog.txt'
    message = _('writing a log message')

Doc/library/glob.rst

@@ -102,7 +102,7 @@ The :mod:`!glob` module defines the following functions:
 .. function:: iglob(pathname, *, root_dir=None, dir_fd=None, recursive=False, \
                     include_hidden=False)
 
-   Return an :term:`iterator` which yields the same values as :func:`glob`
+   Return an :term:`iterator` which yields the same values as :func:`~glob.glob`
    without actually storing them all simultaneously.
 
    .. audit-event:: glob.glob pathname,recursive glob.iglob
@@ -182,7 +182,7 @@ Examples
 
 Consider a directory containing the following files:
 :file:`1.gif`, :file:`2.txt`, :file:`card.gif` and a subdirectory :file:`sub`
-which contains only the file :file:`3.txt`.  :func:`glob` will produce
+which contains only the file :file:`3.txt`.  :func:`~glob.glob` will produce
 the following results.  Notice how any leading components of the path are
 preserved. ::
 

Doc/library/locale.rst

@@ -711,7 +711,7 @@ Access to message catalogs
 .. function:: bind_textdomain_codeset(domain, codeset)
 
 The locale module exposes the C library's gettext interface on systems that
-provide this interface.  It consists of the functions :func:`gettext`,
+provide this interface.  It consists of the functions :func:`~locale.gettext`,
 :func:`dgettext`, :func:`dcgettext`, :func:`textdomain`, :func:`bindtextdomain`,
 and :func:`bind_textdomain_codeset`.  These are similar to the same functions in
 the :mod:`gettext` module, but use the C library's binary format for message

Doc/library/marshal.rst

@@ -58,8 +58,8 @@ this module.  The following types are supported:
   therein are themselves supported.
   Recursive containers are supported since :data:`version` 3.
 * The singletons :const:`None`, :const:`Ellipsis` and :exc:`StopIteration`.
-* :class:`code` objects, if *allow_code* is true. See note above about
-  version dependence.
+* :class:`code <types.CodeType>` objects, if *allow_code* is true. See note
+  above about version dependence.
 
 .. versionchanged:: 3.4