apply pre-commit

Signed-off-by: nstarman <[email protected]>

Author: nstarman

.git-blame-ignore-revs

@@ -4,4 +4,4 @@
 # Move special cases to notes sections
 816fba3b75c38cbb1bb6fe5b1342adc5eab694f3
 0a2fa71a32b924cc92718db29910a6cbbc5e9341
-931144e7d7d5c8b23393aa730ef28962a35b113b
+931144e7d7d5c8b23393aa730ef28962a35b113b

.github/workflows/pages.yml

@@ -45,10 +45,10 @@ jobs:
 
     # Avoid running this workflow for forks and allow skipping CI:
     if: "github.repository == 'data-apis/array-api' && !contains(github.event.head_commit.message, '[ci skip]') && !contains(github.event.head_commit.message, '[skip ci]') && !contains(github.event.head_commit.message, '[skip github]')"
-    
+
     # Define a sequence of job steps...
     steps:
-      
+
       # Checkout the repository:
       - name: 'Checkout repository'
         uses: actions/checkout@v2

CHANGELOG.md

@@ -196,4 +196,4 @@ The following is a list of fixes and points of clarification with regard to the
 - `linspace`: conversion of `start` and `stop` should follow type promotion rules ([gh-568](https://github.com/data-apis/array-api/pull/568))
 - `nonzero`: clarify that, for arrays having a boolean data type, non-zero elements are those elements which equal `True` ([gh-441](https://github.com/data-apis/array-api/pull/441))
 - `trunc`: fix description ([gh-511](https://github.com/data-apis/array-api/pull/511))
-- `vecdot`: clarify broadcasting behavior ([gh-417](https://github.com/data-apis/array-api/pull/417) and [gh-473](https://github.com/data-apis/array-api/pull/473))
+- `vecdot`: clarify broadcasting behavior ([gh-417](https://github.com/data-apis/array-api/pull/417) and [gh-473](https://github.com/data-apis/array-api/pull/473))

CODE_OF_CONDUCT.md

@@ -1,3 +1,3 @@
 Please note that the Consortium for Python Data API Standards has a Code of
 Conduct that we ask everyone to respect, see:
-https://github.com/data-apis/.github/blob/master/CODE_OF_CONDUCT.md
+https://github.com/data-apis/.github/blob/master/CODE_OF_CONDUCT.md

README.md

@@ -241,4 +241,4 @@ Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/d
 
 <!-- ALL-CONTRIBUTORS-LIST:END -->
 
-This project follows the [all-contributors](https://github.com/all-contributors/all-contributors) specification. Contributions of any kind welcome!
+This project follows the [all-contributors](https://github.com/all-contributors/all-contributors) specification. Contributions of any kind welcome!

spec/2021.12/benchmark_suite.md

@@ -1,3 +1,3 @@
 # Benchmark suite
 
-Adding a benchmark suite is planned in the future.
+Adding a benchmark suite is planned in the future.

spec/2021.12/conf.py

@@ -1,5 +1,6 @@
 import sys
 from pathlib import Path
+
 sys.path.insert(0, str(Path(__file__).parents[2] / "src"))
 
 from array_api_stubs import _2021_12 as stubs_mod

spec/2021.12/design_topics/accuracy.rst

@@ -74,4 +74,4 @@ This specification does not specify accuracy requirements for statistical functi
 Linear Algebra
 --------------
 
-This specification does not specify accuracy requirements for linear algebra functions; however, this specification does expect that a conforming implementation of the array API standard will make a best-effort attempt to ensure that its implementations are theoretically sound and numerically robust.
+This specification does not specify accuracy requirements for linear algebra functions; however, this specification does expect that a conforming implementation of the array API standard will make a best-effort attempt to ensure that its implementations are theoretically sound and numerically robust.

spec/2021.12/design_topics/parallelism.rst

@@ -21,4 +21,4 @@ coordination of parallelization behavior in a stack of Python libraries are:
 
 Option (1) may possibly fit in a future version of this array API standard.
 `array-api issue 4 <https://github.com/data-apis/array-api/issues/4>`_ contains
-more detailed discussion on the topic of parallelism.
+more detailed discussion on the topic of parallelism.

spec/2021.12/future_API_evolution.md

@@ -57,4 +57,4 @@ than Python package versioning.
 
 The frequency of releasing a new version of an API standard will likely be at
 regular intervals and on the order of one year, however no assumption on
-frequency of new versions appearing must be made.
+frequency of new versions appearing must be made.