Merge pull request #17798 from anntzer/indent

QuLogic · web-flow · commit a68562aa230e · 2020-06-30T00:55:56.000-04:00
Fix overindented bullet/enumerated lists.
diff --git a/doc/devel/MEP/MEP11.rst b/doc/devel/MEP/MEP11.rst
@@ -127,21 +127,21 @@ dateutil_.
 For binary installations, there are a number of alternatives (here
 ordered from best/hardest to worst/easiest):
 
-    1. The distutils wininst installer allows a post-install script to
-       run.  It might be possible to get this script to run pip_ to
-       install the other dependencies.  (See `this thread
-       <http://grokbase.com/t/python/distutils-sig/109bdnfhp4/distutils-ann-setuptools-post-install-script-for-bdist-wininst>`_
-       for someone who has trod that ground before).
-
-    2. Continue to ship dateutil_, pytz_, six_ and pyparsing_ in
-       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``
-       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.
+1. The distutils wininst installer allows a post-install script to
+   run.  It might be possible to get this script to run pip_ to
+   install the other dependencies.  (See `this thread
+   <http://grokbase.com/t/python/distutils-sig/109bdnfhp4/distutils-ann-setuptools-post-install-script-for-bdist-wininst>`_
+   for someone who has trod that ground before).
+
+2. Continue to ship dateutil_, pytz_, six_ and pyparsing_ in
+   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``
+   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.
 
 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
diff --git a/examples/misc/custom_projection.py b/examples/misc/custom_projection.py
@@ -76,13 +76,13 @@ def _set_lim_and_transforms(self):
 
         # There are three important coordinate spaces going on here:
         #
-        #    1. Data space: The space of the data itself
+        # 1. Data space: The space of the data itself
         #
-        #    2. Axes space: The unit rectangle (0, 0) to (1, 1)
-        #       covering the entire plot area.
+        # 2. Axes space: The unit rectangle (0, 0) to (1, 1)
+        #    covering the entire plot area.
         #
-        #    3. Display space: The coordinates of the resulting image,
-        #       often in pixels or dpi/inch.
+        # 3. Display space: The coordinates of the resulting image,
+        #    often in pixels or dpi/inch.
 
         # This function makes heavy use of the Transform classes in
         # ``lib/matplotlib/transforms.py.`` For more information, see
diff --git a/examples/pie_and_polar_charts/pie_features.py b/examples/pie_and_polar_charts/pie_features.py
@@ -7,11 +7,11 @@
 
 In addition to the basic pie chart, this demo shows a few optional features:
 
-    * slice labels
-    * auto-labeling the percentage
-    * offsetting a slice with "explode"
-    * drop-shadow
-    * custom start angle
+* slice labels
+* auto-labeling the percentage
+* offsetting a slice with "explode"
+* drop-shadow
+* custom start angle
 
 Note about the custom start angle:
 
diff --git a/examples/shapes_and_collections/arrow_guide.py b/examples/shapes_and_collections/arrow_guide.py
@@ -18,9 +18,9 @@
 Here we show three use cases for plotting arrows, depending on whether the
 head or anchor points need to be fixed in data or display space:
 
-    1. Head shape fixed in display space, anchor points fixed in data space
-    2. Head shape and anchor points fixed in display space
-    3. Entire patch fixed in data space
+1. Head shape fixed in display space, anchor points fixed in data space
+2. Head shape and anchor points fixed in display space
+3. Entire patch fixed in data space
 
 Below each use case is presented in turn.
 """
diff --git a/examples/showcase/integral.py b/examples/showcase/integral.py
@@ -5,12 +5,12 @@
 
 Although this is a simple example, it demonstrates some important tweaks:
 
-    * A simple line plot with custom color and line width.
-    * A shaded region created using a Polygon patch.
-    * A text label with mathtext rendering.
-    * figtext calls to label the x- and y-axes.
-    * Use of axis spines to hide the top and right spines.
-    * Custom tick placement and labels.
+* A simple line plot with custom color and line width.
+* A shaded region created using a Polygon patch.
+* A text label with mathtext rendering.
+* figtext calls to label the x- and y-axes.
+* Use of axis spines to hide the top and right spines.
+* Custom tick placement and labels.
 """
 import numpy as np
 import matplotlib.pyplot as plt
diff --git a/examples/statistics/histogram_multihist.py b/examples/statistics/histogram_multihist.py
@@ -5,10 +5,10 @@
 
 Plot histogram with multiple sample sets and demonstrate:
 
-    * Use of legend with multiple sample sets
-    * Stacked bars
-    * Step curve with no fill
-    * Data sets of different sample sizes
+* Use of legend with multiple sample sets
+* Stacked bars
+* Step curve with no fill
+* Data sets of different sample sizes
 
 Selecting different bin counts and sizes can significantly affect the
 shape of a histogram. The Astropy docs have a great section on how to
diff --git a/lib/matplotlib/tests/test_ticker.py b/lib/matplotlib/tests/test_ticker.py
@@ -1113,10 +1113,12 @@ def test_params(self, unicode_minus, input, expected):
         """
         Test the formatting of EngFormatter for various values of the 'places'
         argument, in several cases:
-            0. without a unit symbol but with a (default) space separator;
-            1. with both a unit symbol and a (default) space separator;
-            2. with both a unit symbol and some non default separators;
-            3. without a unit symbol but with some non default separators.
+
+        0. without a unit symbol but with a (default) space separator;
+        1. with both a unit symbol and a (default) space separator;
+        2. with both a unit symbol and some non default separators;
+        3. without a unit symbol but with some non default separators.
+
         Note that cases 2. and 3. are looped over several separator strings.
         """
 
diff --git a/lib/mpl_toolkits/mplot3d/art3d.py b/lib/mpl_toolkits/mplot3d/art3d.py
@@ -44,6 +44,7 @@ def get_dir_vector(zdir):
     ----------
     zdir : {'x', 'y', 'z', None, 3-tuple}
         The direction. Possible values are:
+
         - 'x': equivalent to (1, 0, 0)
         - 'y': equivalent to (0, 1, 0)
         - 'z': equivalent to (0, 0, 1)
@@ -55,7 +56,6 @@ def get_dir_vector(zdir):
     x, y, z : array-like
         The direction vector. This is either a numpy.array or *zdir* itself if
         *zdir* is already a length-3 iterable.
-
     """
     if zdir == 'x':
         return np.array((1, 0, 0))
diff --git a/lib/mpl_toolkits/mplot3d/axes3d.py b/lib/mpl_toolkits/mplot3d/axes3d.py
@@ -2228,9 +2228,10 @@ def add_collection3d(self, col, zs=0, zdir='z'):
         modifying the object and adding z coordinate information.
 
         Supported are:
-            - PolyCollection
-            - LineCollection
-            - PatchCollection
+
+        - PolyCollection
+        - LineCollection
+        - PatchCollection
         """
         zvals = np.atleast_1d(zs)
         zsortval = (np.min(zvals) if zvals.size
@@ -2404,12 +2405,12 @@ def bar3d(self, x, y, z, dx, dy, dz, color=None,
             When coloring the faces of the boxes specifically, this is
             the order of the coloring:
 
-              1. -Z (bottom of box)
-              2. +Z (top of box)
-              3. -Y
-              4. +Y
-              5. -X
-              6. +X
+            1. -Z (bottom of box)
+            2. +Z (top of box)
+            3. -Y
+            4. +Y
+            5. -X
+            6. +X
 
         zsort : str, optional
             The z-axis sorting scheme passed onto `~.art3d.Poly3DCollection`
@@ -2724,16 +2725,16 @@ def voxels(self, *args, facecolors=None, edgecolors=None, shade=True,
         facecolors, edgecolors : array-like, optional
             The color to draw the faces and edges of the voxels. Can only be
             passed as keyword arguments.
-            This parameter can be:
-
-              - A single color value, to color all voxels the same color. This
-                can be either a string, or a 1D rgb/rgba array
-              - ``None``, the default, to use a single color for the faces, and
-                the style default for the edges.
-              - A 3D ndarray of color names, with each item the color for the
-                corresponding voxel. The size must match the voxels.
-              - A 4D ndarray of rgb/rgba data, with the components along the
-                last axis.
+            These parameters can be:
+
+            - A single color value, to color all voxels the same color. This
+              can be either a string, or a 1D rgb/rgba array
+            - ``None``, the default, to use a single color for the faces, and
+              the style default for the edges.
+            - A 3D ndarray of color names, with each item the color for the
+              corresponding voxel. The size must match the voxels.
+            - A 4D ndarray of rgb/rgba data, with the components along the
+              last axis.
 
         shade : bool, default: True
             Whether to shade the facecolors.  Shading is always disabled when
diff --git a/tutorials/intermediate/legend_guide.py b/tutorials/intermediate/legend_guide.py
@@ -166,13 +166,12 @@
 # appropriate :class:`~matplotlib.legend_handler.HandlerBase` subclass.
 # The choice of handler subclass is determined by the following rules:
 #
-#     1. Update :func:`~matplotlib.legend.Legend.get_legend_handler_map`
-#        with the value in the ``handler_map`` keyword.
-#     2. Check if the ``handle`` is in the newly created ``handler_map``.
-#     3. Check if the type of ``handle`` is in the newly created
-#        ``handler_map``.
-#     4. Check if any of the types in the ``handle``'s mro is in the newly
-#        created ``handler_map``.
+# 1. Update :func:`~matplotlib.legend.Legend.get_legend_handler_map`
+#    with the value in the ``handler_map`` keyword.
+# 2. Check if the ``handle`` is in the newly created ``handler_map``.
+# 3. Check if the type of ``handle`` is in the newly created ``handler_map``.
+# 4. Check if any of the types in the ``handle``'s mro is in the newly
+#    created ``handler_map``.
 #
 # For completeness, this logic is mostly implemented in
 # :func:`~matplotlib.legend.Legend.get_legend_handler`.

Original file line number	Diff line number	Diff line change
`@@ -76,13 +76,13 @@ def _set_lim_and_transforms(self):`
`76`	`76`
`77`	`77`	`# There are three important coordinate spaces going on here:`
`78`	`78`	`#`
`79`		`- # 1. Data space: The space of the data itself`
	`79`	`+ # 1. Data space: The space of the data itself`
`80`	`80`	`#`
`81`		`- # 2. Axes space: The unit rectangle (0, 0) to (1, 1)`
`82`		`- # covering the entire plot area.`
	`81`	`+ # 2. Axes space: The unit rectangle (0, 0) to (1, 1)`
	`82`	`+ # covering the entire plot area.`
`83`	`83`	`#`
`84`		`- # 3. Display space: The coordinates of the resulting image,`
`85`		`- # often in pixels or dpi/inch.`
	`84`	`+ # 3. Display space: The coordinates of the resulting image,`
	`85`	`+ # often in pixels or dpi/inch.`
`86`	`86`
`87`	`87`	`# This function makes heavy use of the Transform classes in`
`88`	`88`	# ``lib/matplotlib/transforms.py.`` For more information, see