Fix more missing references. (matplotlib#16115)

Fix more missing references.

Author: anntzer

doc/api/prev_api_changes/api_changes_3.0.0.rst

@@ -65,7 +65,7 @@ This new default may be overridden in either of three ways:
 ------------------------------------------------------------------
 
 `Text.set_text` when passed a string value of ``None`` would set the
-string to ``"None"``, so subsequent calls to `Text.get_text` would return
+string to ``"None"``, so subsequent calls to `.Text.get_text` would return
 the ambiguous ``"None"`` string.
 
 This change sets text objects passed ``None`` to have empty strings, so that
@@ -106,7 +106,7 @@ Different exception types for undocumented options
 - Passing the undocumented ``xmin`` or ``xmax`` arguments to
   :meth:`~matplotlib.axes.Axes.set_xlim` would silently override the ``left``
   and ``right`` arguments.  :meth:`~matplotlib.axes.Axes.set_ylim` and the
-  3D equivalents (e.g. :meth:`~mpl_toolkits.axes.Axes3D.set_zlim3d`) had a
+  3D equivalents (e.g. `~.Axes3D.set_zlim3d`) had a
   corresponding problem.
   A ``TypeError`` will be raised if they would override the earlier
   limit arguments.  In 3.0 these were kwargs were deprecated, but in 3.1
@@ -116,14 +116,14 @@ Different exception types for undocumented options
 Improved call signature for ``Axes.margins``
 --------------------------------------------
 
-:meth:`matplotlib.axes.Axes.margins` and :meth:`mpl_toolkits.mplot3d.Axes3D.margins`
+`.Axes.margins` and `.Axes3D.margins`
 no longer accept arbitrary keywords. ``TypeError`` will therefore be raised
 if unknown kwargs are passed; previously they would be silently ignored.
 
 If too many positional arguments are passed, ``TypeError`` will be raised
 instead of ``ValueError``, for consistency with other call-signature violations.
 
-``Axes3D.margins`` now raises ``TypeError`` instead of emitting a deprecation
+`.Axes3D.margins` now raises ``TypeError`` instead of emitting a deprecation
 warning if only two positional arguments are passed.  To supply only ``x`` and
 ``y`` margins, use keyword arguments.
 
@@ -140,7 +140,7 @@ now raise ``TypeError`` because ``**kwargs`` has been removed.
 
 - :meth:`matplotlib.axes.Axes.stem` no longer accepts unknown keywords,
   and raises ``TypeError`` instead of emitting a deprecation.
-- :meth:`matplotlib.axex.Axes.stem` now raises TypeError when passed
+- :meth:`matplotlib.axes.Axes.stem` now raises TypeError when passed
   unhandled positional arguments.  If two or more arguments are passed
   (ie X, Y, [linefmt], ...) and Y cannot be cast to an array, an error
   will be raised instead of treating X as Y and Y as linefmt.
@@ -161,18 +161,18 @@ Non-interactive FigureManager classes are now aliases of FigureManagerBase
 --------------------------------------------------------------------------
 
 The `FigureManagerPdf`, `FigureManagerPS`, and `FigureManagerSVG` classes,
-which were previously empty subclasses of `FigureManagerBase` (i.e., not
+which were previously empty subclasses of `.FigureManagerBase` (i.e., not
 adding or overriding any attribute or method), are now direct aliases for
-`FigureManagerBase`.
+`.FigureManagerBase`.
 
 
 Change to the output of `.image.thumbnail`
 ------------------------------------------
 
 When called with ``preview=False``, `.image.thumbnail` previously returned an
 figure whose canvas class was set according to the output file extension.  It
-now returns a figure whose canvas class is the base `FigureCanvasBase` (and
-relies on `FigureCanvasBase.print_figure`) to handle the canvas switching
+now returns a figure whose canvas class is the base `.FigureCanvasBase` (and
+relies on `.FigureCanvasBase.print_figure`) to handle the canvas switching
 properly).
 
 As a side effect of this change, `.image.thumbnail` now also supports .ps, .eps,
@@ -204,7 +204,7 @@ When contour is called with levels specified as a target number rather
 than a list, and the 'extend' kwarg is used, the levels are now chosen
 such that some data typically will fall in the extended range.
 
-When contour is called with a `LogNorm` or a `LogLocator`, it will now
+When contour is called with a `.LogNorm` or a `.LogLocator`, it will now
 select colors using the geometric mean rather than the arithmetic mean
 of the contour levels.
 
@@ -216,8 +216,8 @@ A bug was fixed where the last row and column of data in
 `~.Axes.axes.streamplot` were being dropped.
 
 
-Changed default `AutoDateLocator` kwarg *interval_multiples* to ``True``
-------------------------------------------------------------------------
+Changed default `.AutoDateLocator` kwarg *interval_multiples* to ``True``
+-------------------------------------------------------------------------
 
 The default value of the tick locator for dates, `.dates.AutoDateLocator`
 kwarg *interval_multiples* was set to ``False`` which leads to not-nice
@@ -278,7 +278,7 @@ original behavior.
 Colorbar for log-scaled hexbin
 ------------------------------
 
-When using `hexbin` and plotting with a logarithmic color scale, the colorbar
+When using `~.Axes.hexbin` and plotting with a logarithmic color scale, the colorbar
 ticks are now correctly log scaled. Previously the tick values were linear
 scaled log(number of counts).
 
@@ -292,10 +292,11 @@ regardless of the default color. However, this means that there is no way to
 fall back on the default color of the renderer.
 
 
-Blacklisted rcparams no longer updated by `rcdefaults`, `rc_file_defaults`, `rc_file`
--------------------------------------------------------------------------------------
+Blacklisted rcparams no longer updated by `~matplotlib.rcdefaults`, `~matplotlib.rc_file_defaults`, `~matplotlib.rc_file`
+-------------------------------------------------------------------------------------------------------------------------
 
-The rc modifier functions `rcdefaults`, `rc_file_defaults` and `rc_file`
+The rc modifier functions `~matplotlib.rcdefaults`,
+`~matplotlib.rc_file_defaults` and `~matplotlib.rc_file`
 now ignore rcParams in the `matplotlib.style.core.STYLE_BLACKLIST` set.  In
 particular, this prevents the ``backend`` and ``interactive`` rcParams from
 being incorrectly modified by these functions.
@@ -328,7 +329,7 @@ Return type of ArtistInspector.get_aliases changed
 was used to simulate a set in earlier versions of Python.  It has now been
 replaced by a set, i.e. ``{fullname: {alias1, alias2, ...}}``.
 
-This value is also stored in `ArtistInspector.aliasd`, which has likewise
+This value is also stored in `.ArtistInspector.aliasd`, which has likewise
 changed.
 
 
@@ -349,10 +350,10 @@ Modules
 ```````
 The following modules are deprecated:
 
-- :mod:`matplotlib.compat.subprocess`. This was a python 2 workaround, but all
+- ``matplotlib.compat.subprocess``. This was a python 2 workaround, but all
   the functionality can now be found in the python 3 standard library
   :mod:`subprocess`.
-- :mod:`matplotlib.backends.wx_compat`. Python 3 is only compatible with
+- ``matplotlib.backends.wx_compat``. Python 3 is only compatible with
   wxPython 4, so support for wxPython 3 or earlier can be dropped.
 
 Classes, methods, functions, and attributes
@@ -382,7 +383,7 @@ The following classes, methods, functions, and attributes are deprecated:
 - ``font_manager.TempCache``
 - ``image._ImageBase.iterpnames``, use the ``interpolation_names`` property
   instead. (this affects classes that inherit from ``_ImageBase`` including
-  :class:`FigureImage`, :class:`BboxImage`, and :class:`AxesImage`)
+  `.FigureImage`, `.BboxImage`, and `.AxesImage`)
 - ``mathtext.unichr_safe`` (use ``chr`` instead)
 - ``patches.Polygon.xy``
 - ``table.Table.get_child_artists`` (use ``get_children`` instead)
@@ -395,7 +396,7 @@ The following classes, methods, functions, and attributes are deprecated:
 - ``FigureCanvasWx.macros``
 - ``_ImageBase.iterpnames``, use the ``interpolation_names`` property instead.
   (this affects classes that inherit from ``_ImageBase`` including
-  :class:`FigureImage`, :class:`BboxImage`, and :class:`AxesImage`)
+  `.FigureImage`, `.BboxImage`, and `.AxesImage`)
 - ``patches.Polygon.xy``
 - ``texmanager.dvipng_hack_alpha``
 - ``text.Annotation.arrow``

doc/api/prev_api_changes/api_changes_3.0.1.rst

@@ -9,13 +9,13 @@ subplotparams will collapse axes to zero width or height.  This prevents
 To improve import (startup) time, private modules are now imported lazily.
 These modules are no longer available at these locations:
 
-  - `matplotlib.backends.backend_agg._png`
-  - `matplotlib.contour._contour`
-  - `matplotlib.image._png`
-  - `matplotlib.mathtext._png`
-  - `matplotlib.testing.compare._png`
-  - `matplotlib.texmanager._png`
-  - `matplotlib.tri.triangulation._tri`
-  - `matplotlib.tri.triangulation._qhull`
-  - `matplotlib.tri.tricontour._tri`
-  - `matplotlib.tri.trifinder._tri`
+- ``matplotlib.backends.backend_agg._png``
+- ``matplotlib.contour._contour``
+- ``matplotlib.image._png``
+- ``matplotlib.mathtext._png``
+- ``matplotlib.testing.compare._png``
+- ``matplotlib.texmanager._png``
+- ``matplotlib.tri.triangulation._tri``
+- ``matplotlib.tri.triangulation._qhull``
+- ``matplotlib.tri.tricontour._tri``
+- ``matplotlib.tri.trifinder._tri``

doc/api/prev_api_changes/api_changes_3.1.0.rst

@@ -29,10 +29,10 @@ Invalid points in PathCollections
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 PathCollections created with `~.Axes.scatter` now keep track of invalid points.
 Previously, points with nonfinite (infinite or nan) coordinates would not be
-included in the offsets (as returned by `PathCollection.get_offsets`) of a
-`PathCollection` created by `~.Axes.scatter`, and points with nonfinite values
+included in the offsets (as returned by `.PathCollection.get_offsets`) of a
+`.PathCollection` created by `~.Axes.scatter`, and points with nonfinite values
 (as specified by the *c* kwarg) would not be included in the array (as returned
-by `PathCollection.get_array`)
+by `.PathCollection.get_array`)
 
 Such points are now included, but masked out by returning a masked array.
 
@@ -56,9 +56,9 @@ instead of adding a decade only to the right.
 
 Log-scaled axes
 ~~~~~~~~~~~~~~~
-When the default `LogLocator` would generate no ticks for an axis (e.g., an
+When the default `.LogLocator` would generate no ticks for an axis (e.g., an
 axis with limits from 0.31 to 0.39) or only a single tick, it now instead falls
-back on the linear `AutoLocator` to pick reasonable tick positions.
+back on the linear `.AutoLocator` to pick reasonable tick positions.
 
 `.Figure.add_subplot` with no arguments
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -124,7 +124,7 @@ would be::
 
 usetex support
 ~~~~~~~~~~~~~~
-Previously, if :rc:`text.usetex` was True, then constructing a `TextPath` on
+Previously, if :rc:`text.usetex` was True, then constructing a `.TextPath` on
 a non-mathtext string with ``usetex=False`` would rely on the mathtext parser
 (but not on usetex support!) to parse the string.  The mathtext parser is not
 invoked anymore, which may cause slight changes in glyph positioning.
@@ -247,9 +247,9 @@ return 2 lists of histogram values. Previously, a single list was returned.
 `.backend_bases.Timer.remove_callback` future signature change
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Currently, `.backend_bases.Timer.remove_callback(func, *args,
-**kwargs)` removes a callback previously added by
-`.backend_bases.Timer.add_callback(func, *args, **kwargs)`, but if
+Currently, ``backend_bases.Timer.remove_callback(func, *args,
+**kwargs)`` removes a callback previously added by
+``backend_bases.Timer.add_callback(func, *args, **kwargs)``, but if
 ``*args, **kwargs`` is not passed in (ex,
 ``Timer.remove_callback(func)``), then the first callback with a
 matching ``func`` is removed, regardless of whether it was added with
@@ -277,7 +277,7 @@ The new API is modelled after `atexit.register` / `atexit.unregister`.
 `~.collections.LineCollection` object instead of a list of
 `~.lines.Line2D` objects for stem lines plotted using
 `~.Axes.stem`. This gives a very large performance boost to displaying
-and moving `~Axes.stem` plots.
+and moving `~.Axes.stem` plots.
 
 This will become the default behaviour in Matplotlib 3.3. To use it
 now, the *use_line_collection* keyword argument to `~.Axes.stem` can
@@ -299,7 +299,7 @@ retrieve the collection properties.
 `.cm.ScalarMappable`.  This inheritance lead to a confusing situation
 where the `.cm.ScalarMappable` passed to `matplotlib.colorbar.Colorbar`
 (`~.Figure.colorbar`) had a ``set_norm`` method, as did the colorbar.
-The colorbar is now purely a follower to the `ScalarMappable` norm and
+The colorbar is now purely a follower to the `.ScalarMappable` norm and
 colormap, and the old inherited methods
 `~matplotlib.colorbar.ColorbarBase.set_norm`,
 `~matplotlib.colorbar.ColorbarBase.set_cmap`,
@@ -364,7 +364,7 @@ them.
 Furthermore, `.Axes.spy` spy does now allow for an *extent* argument
 (was silently ignored so far).
 
-A bug with `.Axes.spy(..., origin='lower')` is fixed.  Previously this
+A bug with ``Axes.spy(..., origin='lower')`` is fixed.  Previously this
 flipped the data but not the y-axis resulting in a mismatch between
 axes labels and actual data indices. Now, *origin='lower'* flips both
 the data and the y-axis labels.
@@ -383,7 +383,7 @@ limits, ticks, and tick labels.
 
 MouseEvents
 ~~~~~~~~~~~
-MouseEvents now include the event name in their `str()`.
+MouseEvents now include the event name in their ``str()``.
 Previously they contained the prefix "MPL MouseEvent".
 
 RGBA buffer return type
@@ -411,8 +411,8 @@ non-callable), the exception would be silently ignored and the default
 formatter be used instead.  This is no longer the case; the exception
 is now propagated out.
 
-Deprecation of redundant `Tick` attributes
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Deprecation of redundant `.Tick` attributes
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 The ``gridOn``, ``tick1On``, ``tick2On``, ``label1On``, and ``label2On``
 `~.Tick` attributes have been deprecated.  Directly get and set the visibility
@@ -734,7 +734,7 @@ Deprecations
 - The ``\stackrel`` mathtext command hsa been deprecated (it behaved differently
   from LaTeX's ``\stackrel``.  To stack two mathtext expressions, use
   ``\genfrac{left-delim}{right-delim}{fraction-bar-thickness}{}{top}{bottom}``.
-- The `\mathcircled` mathtext command (which is not a real TeX command)
+- The ``\mathcircled`` mathtext command (which is not a real TeX command)
   is deprecated.  Directly use unicode characters (e.g.
   ``"\N{CIRCLED LATIN CAPITAL LETTER A}"`` or ``"\u24b6"``) instead.
 - Support for setting :rc:`mathtext.default` to circled is deprecated.
@@ -796,7 +796,7 @@ Changes in parameter names
   as a keyword argument. The common usage pattern as a positional argument
   ``matplotlib.use('Qt5Agg')`` is not affected.
 - The *normed* parameter to `Axes.hist2d` has been renamed to *density*.
-- The *s* parameter to `Annotation` (and indirectly `Axes.annotation`) has
+- The *s* parameter to `.Annotation` (and indirectly `Axes.annotation`) has
   been renamed to *text*.
 - The *tolerence* parameter to
   `bezier.find_bezier_t_intersecting_with_closedpath`,
@@ -946,7 +946,7 @@ Testing
 
 - ``matplotlib.testing.decorators.switch_backend`` decorator
 
-Test functions should use `pytest.mark.backend(...)`, and the mark will be
+Test functions should use ``pytest.mark.backend``, and the mark will be
 picked up by the `matplotlib.testing.conftest.mpl_test_settings` fixture.
 
 Quiver
@@ -998,7 +998,7 @@ Transforms / scales
 - ``InvertedLog2Transform``
 - ``InvertedNaturalLogTransform``
 
-These classes defined in :mod:`matplotlib.scales` are deprecated.
+These classes defined in :mod:`matplotlib.scale` are deprecated.
 As a replacement, use the general `LogTransform` and `InvertedLogTransform`
 classes, whose constructors take a *base* argument.
 
@@ -1069,7 +1069,7 @@ Environmental Variables
 Axis
 ~~~~
 
-- `.Axis.iter_ticks`
+- ``Axis.iter_ticks``
 
 This only served as a helper to the private `.Axis._update_ticks`
 

doc/api/prev_api_changes/api_changes_3.2.0/behavior.rst

@@ -171,7 +171,7 @@ an axis limit did not coincide with a sticky edge, it cannot *cross* a sticky
 edge through margin application -- instead, the margins will only expand the
 axis limit until it bumps against the sticky edge.
 
-This change improves the margins of axes displaying a `~Axes.streamplot`:
+This change improves the margins of axes displaying a `~.Axes.streamplot`:
 
 - if the streamplot goes all the way to the edges of the vector field, then the
   axis limits are set to match exactly the vector field limits (whereas they
@@ -201,9 +201,9 @@ that Times New Roman Bold is now correctly detected as bold, not normal weight.
 
 Color-like checking
 ~~~~~~~~~~~~~~~~~~~
-`matplotlib.color.is_colorlike()` used to return True for all string
+`matplotlib.colors.is_color_like` used to return True for all string
 representations of floats. However, only those with values in 0-1 are valid
-colors (representing grayscale values). ``is_colorlike()`` now returns False
+colors (representing grayscale values). `.is_color_like` now returns False
 for string representations of floats outside 0-1.
 
 Default image interpolation
@@ -243,7 +243,7 @@ for better readability.
 
 ``add_subplot()``
 ~~~~~~~~~~~~~~~~~
-`.Figure.add_subplot()` and `.pyplot.subplot()` do not accept a `figure`
+`.Figure.add_subplot()` and `.pyplot.subplot()` do not accept a *figure*
 keyword argument anymore. It only used to work anyway if the passed figure
 was ``self`` or the current figure, respectively.
 

doc/api/prev_api_changes/api_changes_3.2.0/development.rst

@@ -3,7 +3,7 @@ Development changes
 
 Windows build
 ~~~~~~~~~~~~~
-Previously, when building the :mod:`matplotlib._png` extension, the build
+Previously, when building the ``matplotlib._png`` extension, the build
 script would add "png" and "z" to the extensions ``.libraries`` attribute (if
 pkg-config information is not available, which is in particular the case on
 Windows).

doc/devel/MEP/MEP10.rst

@@ -30,7 +30,7 @@ There should instead be short summary tables that link to detailed
 documentation.  In addition, some of the docstrings themselves are
 quite long and contain redundant information.
 
-Building the documentation takes a long time and uses a `make.py`
+Building the documentation takes a long time and uses a :file:`make.py`
 script rather than a Makefile.
 
 Detailed description
@@ -163,17 +163,17 @@ Implementation
    This should hopefully have minimal impact on the narrative
    documentation.
 
-4. Modify the example page generator (`gen_rst.py`) so that it
+4. Modify the example page generator (:file:`gen_rst.py`) so that it
    extracts the module docstring from the example and includes it in a
    non-literal part of the example page.
 
 5. Use `sphinx-quickstart` to generate a new-style Sphinx Makefile.
-   The following features in the current `make.py` will have to be
+   The following features in the current :file:`make.py` will have to be
    addressed in some other way:
 
-    - Copying of some static content
+   - Copying of some static content
 
-    - Specifying a "small" build (only low-resolution PNG files for examples)
+   - Specifying a "small" build (only low-resolution PNG files for examples)
 
 Steps 1, 2, and 3 are interdependent.  4 and 5 may be done
 independently, though 5 has some dependency on 3.

doc/devel/MEP/MEP11.rst

@@ -137,11 +137,11 @@ ordered from best/hardest to worst/easiest):
        our installer, but use the post-install-script to install them
        *only* if they can not already be found.
 
-    3. Move all of these packages inside a (new) `matplotlib.extern`
+    3. Move all of these packages inside a (new) ``matplotlib.extern``
        namespace so it is clear for outside users that these are
        external packages.  Add some conditional imports in the core
        matplotlib codebase so dateutil_ (at the top-level) is tried
-       first, and failing that `matplotlib.extern.dateutil` is used.
+       first, and failing that ``matplotlib.extern.dateutil`` is used.
 
 2 and 3 are undesirable as they still require maintaining copies of
 these packages in our tree -- and this is exacerbated by the fact that