STY: Apply end-of-file-fixer pre-commit hook

matthewfeickert · matthewfeickert · commit c1a33a481b9c · 2022-04-13T18:09:05.000-05:00
diff --git a/.github/workflows/tests.yml b/.github/workflows/tests.yml
@@ -305,4 +305,4 @@ jobs:
           pinned: false
           close-previous: false
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
diff --git a/README.rst b/README.rst
@@ -116,4 +116,3 @@ For more information, please visit `the informational page
 <https://sustainable-open-science-and-software.github.io/>`__ or download the
 `participant information sheet
 <https://sustainable-open-science-and-software.github.io/assets/PIS_sustainable_software.pdf>`__.
-
diff --git a/doc/_static/.gitignore b/doc/_static/.gitignore
@@ -2,4 +2,3 @@ contour_frontpage.png
 histogram_frontpage.png
 membrane_frontpage.png
 surface3d_frontpage.png
-
diff --git a/doc/_static/switcher.json b/doc/_static/switcher.json
@@ -19,4 +19,4 @@
         "name": "2.2",
         "version": "2.2.4"
     },
-]
+]
diff --git a/doc/api/_enums_api.rst b/doc/api/_enums_api.rst
@@ -12,4 +12,3 @@
    .. autoclass:: CapStyle
       :members: demo
       :exclude-members: butt, round, projecting, input_description
-
diff --git a/doc/api/lines_api.rst b/doc/api/lines_api.rst
@@ -26,4 +26,4 @@ Functions
    :template: autosummary.rst
 
    segment_hits
-   
+   
diff --git a/doc/api/next_api_changes/behavior/22639-RA.rst b/doc/api/next_api_changes/behavior/22639-RA.rst
@@ -2,4 +2,4 @@ MacOSX backend to use sRGB instead of GenericRGB colorspace
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 MacOSX backend now display sRGB tagged image instead of GenericRGB which is
 an older (now deprecated) Apple colorspace. This is the source colorspace
-used by ColorSync to convert to the current display profile.
+used by ColorSync to convert to the current display profile.
diff --git a/doc/api/next_api_changes/behavior/22691-JMK.rst b/doc/api/next_api_changes/behavior/22691-JMK.rst
@@ -3,4 +3,4 @@ QuadMesh mouseover defaults to False
 
 New in 3.5, `.QuadMesh.get_cursor_data` allows display of data values
 under the cursor.  However, this can be very slow for large meshes, so
-by `.QuadMesh.set_mouseover` defaults to *False*.
+by `.QuadMesh.set_mouseover` defaults to *False*.
diff --git a/doc/api/next_api_changes/deprecations/22133-OG.rst b/doc/api/next_api_changes/deprecations/22133-OG.rst
@@ -3,4 +3,4 @@
 
 The modules ``matplotlib.AFM``, ``matplotlib.configfont_pattern``, and
 ``matplotlib.Type1Font`` are considered internal and public access is
-deprecated.
+deprecated.
diff --git a/doc/api/next_api_changes/deprecations/22134-OG.rst b/doc/api/next_api_changes/deprecations/22134-OG.rst
@@ -2,4 +2,4 @@ Modules ``tight_bbox`` and ``tight_layout`` deprecated
 ------------------------------------------------------
 
 The modules ``matplotlib.tight_bbox`` and ``matplotlib.tight_layout`` are
-considered internal and public access is deprecated.
+considered internal and public access is deprecated.
diff --git a/doc/api/next_api_changes/deprecations/22268-OG.rst b/doc/api/next_api_changes/deprecations/22268-OG.rst
@@ -7,4 +7,4 @@ is deprecated.
 
 For ``is_close_to_int`` use ``math.isclose(x, round(x))`` instead.
 For ``is_decade`` use
-``y = numpy.log(x)/numpy.log(base); numpy.isclose(y, numpy.round(y))``
+``y = numpy.log(x)/numpy.log(base); numpy.isclose(y, numpy.round(y))``
diff --git a/doc/api/next_api_changes/deprecations/22345-JK.rst b/doc/api/next_api_changes/deprecations/22345-JK.rst
@@ -11,4 +11,4 @@ The methods `~.Figure.set_constrained_layout_pads` and
 `~.Figure.get_constrained_layout_pads` are will be deprecated in favor of
 ``figure.get_layout_engine().set()`` and
 ``figure.get_layout_engine().get()``, and currently emit a
-``PendingDeprecationWarning``.
+``PendingDeprecationWarning``.
diff --git a/doc/api/next_api_changes/development/22205-ES.rst b/doc/api/next_api_changes/development/22205-ES.rst
@@ -13,4 +13,3 @@ being bumped:
 
 This is consistent with our :ref:`min_deps_policy` and `NEP29
 <https://numpy.org/neps/nep-0029-deprecation_policy.html>`__
-
diff --git a/doc/api/next_api_changes/removals/21980-CC.rst b/doc/api/next_api_changes/removals/21980-CC.rst
@@ -3,4 +3,4 @@ Removed loaded modules logging
 
 The list of currently loaded modules is no longer logged at the DEBUG level at Matplotlib import time,
 because it can produce extensive output and make other valuable DEBUG statements difficult to find. 
-If you were relying on this please arrange for your own logging (the built-in `sys.modules` can be used to get the currently loaded modules).
+If you were relying on this please arrange for your own logging (the built-in `sys.modules` can be used to get the currently loaded modules).
diff --git a/doc/api/next_api_changes/removals/22516-OG.rst b/doc/api/next_api_changes/removals/22516-OG.rst
@@ -17,4 +17,4 @@ be used as a replacement.
 
 In the WX backend, the property ``IDLE_DELAY`` is removed. In addition, the
 parameter ``origin`` of ``gui_repaint()`` is removed, as well as the method
-``get_canvas()``. No replacements are provided.
+``get_canvas()``. No replacements are provided.
diff --git a/doc/api/toolkits/mplot3d/faq.rst b/doc/api/toolkits/mplot3d/faq.rst
@@ -49,4 +49,3 @@ Work is being done to eliminate this issue. For matplotlib v1.1.0, there is
 a semi-official manner to modify these parameters. See the note in the
 :mod:`.mplot3d.axis3d` section of the mplot3d API documentation for
 more information.
-
diff --git a/doc/api/transformations.rst b/doc/api/transformations.rst
@@ -15,4 +15,3 @@
        interval_contains, interval_contains_open
    :show-inheritance:
    :special-members:
-
diff --git a/doc/devel/style_guide.rst b/doc/devel/style_guide.rst
@@ -406,4 +406,3 @@ resources contain common best practices for writing documentation.
 * `Google Developer Style Guide <https://developers.google.com/style>`_
 * `IBM Style Guide <https://www.oreilly.com/library/view/the-ibm-style/9780132118989/>`_
 * `Red Hat Style Guide <https://stylepedia.net/style/#grammar>`_
-
diff --git a/doc/devel/testing.rst b/doc/devel/testing.rst
@@ -256,4 +256,3 @@ The test discovery scope can be narrowed to single test modules or even single
 functions::
 
     python -m pytest --pyargs matplotlib.tests.test_simplification.py::test_clipping
-
diff --git a/doc/missing-references.json b/doc/missing-references.json
@@ -1107,4 +1107,4 @@
       "lib/mpl_toolkits/mplot3d/axes3d.py:docstring of mpl_toolkits.mplot3d.axes3d.Axes3D.get_ylim3d:24"
     ]
   }
-}
+}
diff --git a/doc/users/next_whats_new/inset_axes_improvements.rst b/doc/users/next_whats_new/inset_axes_improvements.rst
@@ -3,4 +3,4 @@ Axes.inset_axes Flexibility
 
 `matplotlib.axes.Axes.inset_axes` now accepts the *projection*, *polar* and
 *axes_class* keyword arguments, so that subclasses of `matplotlib.axes.Axes` may
-be returned.
+be returned.
diff --git a/doc/users/next_whats_new/layout_engine.rst b/doc/users/next_whats_new/layout_engine.rst
@@ -4,4 +4,4 @@ New ``layout_engine`` module
 Matplotlib ships with ``tight_layout`` and ``constrained_layout`` layout
 engines.  A new ``layout_engine`` module is provided to allow downstream
 libraries to write their own layout engines and `~.figure.Figure` objects can
-now take a `.LayoutEngine` subclass as an argument to the *layout* parameter.
+now take a `.LayoutEngine` subclass as an argument to the *layout* parameter.
diff --git a/doc/users/next_whats_new/list_font_names.rst b/doc/users/next_whats_new/list_font_names.rst
@@ -7,4 +7,4 @@ available font names in matplotlib with:
 .. code-block:: python
 
     from matplotlib import font_manager
-    font_manager.get_font_names()
+    font_manager.get_font_names()
diff --git a/doc/users/next_whats_new/modify_stairs_fill_edge_behaviour.rst b/doc/users/next_whats_new/modify_stairs_fill_edge_behaviour.rst
@@ -6,4 +6,4 @@ edge by setting edgecolor="none". Calling ``set_color()``
 on the Patch after would make the Patch appear larger. 
 Updated treatment prevents this. Likewise calling 
 ``stairs(..., fill=True, lw=3)`` will behave more 
-transparently.
+transparently.
diff --git a/doc/users/next_whats_new/windows_arm64.rst b/doc/users/next_whats_new/windows_arm64.rst
@@ -5,4 +5,4 @@ Preliminary support for windows on arm64 target added.
 
 Matplotlib for windows/arm64 requires FreeType 2.11 or above.
 
-No binary wheels are available yet but can be built from source.
+No binary wheels are available yet but can be built from source.
diff --git a/lib/matplotlib/backends/web_backend/css/page.css b/lib/matplotlib/backends/web_backend/css/page.css
@@ -80,4 +80,3 @@ span#login_widget {
     margin: 10px;
     vertical-align: top;
 }
-
diff --git a/lib/matplotlib/tests/README b/lib/matplotlib/tests/README
@@ -6,4 +6,3 @@ the Testing section of the Matplotlib Developers’ Guide:
 
 * https://matplotlib.org/devel/testing.html
 * <mpl_source_dir>/doc/devel/coding_guide.rst (equivalent, but in reST format)
-
diff --git a/plot_types/README.rst b/plot_types/README.rst
@@ -9,4 +9,4 @@ Overview of many common plotting commands in Matplotlib.
 
 Note that we have stripped all labels, but they are present by default.
 See the `gallery <../gallery/index.html>`_ for many more examples and
-the `tutorials page <../tutorials/index.html>`_ for longer examples.
+the `tutorials page <../tutorials/index.html>`_ for longer examples.
diff --git a/plot_types/arrays/README.rst b/plot_types/arrays/README.rst
@@ -3,4 +3,4 @@
 Plots of arrays and fields
 --------------------------
 
-Plotting for arrays of data ``Z(x, y)`` and fields ``U(x, y), V(x, y)``.
+Plotting for arrays of data ``Z(x, y)`` and fields ``U(x, y), V(x, y)``.
diff --git a/plot_types/basic/README.rst b/plot_types/basic/README.rst
@@ -3,4 +3,4 @@
 Basic
 -----
 
-Basic plot types, usually y versus x.
+Basic plot types, usually y versus x.
diff --git a/plot_types/stats/README.rst b/plot_types/stats/README.rst
@@ -3,4 +3,4 @@
 Statistics plots
 ----------------
 
-Plots for statistical analysis.
+Plots for statistical analysis.
diff --git a/plot_types/unstructured/README.rst b/plot_types/unstructured/README.rst
@@ -6,4 +6,4 @@ Unstructured coordinates
 Sometimes we collect data ``z`` at coordinates ``(x,y)`` and want to visualize
 as a contour.  Instead of gridding the data and then using 
 `~.axes.Axes.contour`, we can use a triangulation algorithm and fill the 
-triangles.
+triangles.
