Run pre-commit

Author: dstansby

.github/workflows/test_and_deploy.yml

@@ -3,7 +3,7 @@
 
 name: tests
 
-on: 
+on:
   push:
     branches:
       - main
@@ -65,7 +65,7 @@ jobs:
 
   deploy:
     # this will run when you have tagged a commit, starting with "v*"
-    # and requires that you have put your twine API key in your 
+    # and requires that you have put your twine API key in your
     # github secrets (see readme for details)
     needs: [test]
     runs-on: ubuntu-latest
@@ -88,4 +88,3 @@ jobs:
           git tag
           python -m build .
           twine upload dist/*
-

.gitignore

@@ -82,4 +82,3 @@ venv/
 
 # written by setuptools_scm
 **/_version.py
-

.napari/DESCRIPTION.md

@@ -5,18 +5,18 @@ the functionality of your plugin. Its content will be rendered on your plugin's
 napari hub page.
 
 The sections below are given as a guide for the flow of information only, and
-are in no way prescriptive. You should feel free to merge, remove, add and 
-rename sections at will to make this document work best for your plugin. 
+are in no way prescriptive. You should feel free to merge, remove, add and
+rename sections at will to make this document work best for your plugin.
 
 ## Description
 
-This should be a detailed description of the context of your plugin and its 
+This should be a detailed description of the context of your plugin and its
 intended purpose.
 
 If you have videos or screenshots of your plugin in action, you should include them
-here as well, to make them front and center for new users. 
+here as well, to make them front and center for new users.
 
-You should use absolute links to these assets, so that we can easily display them 
+You should use absolute links to these assets, so that we can easily display them
 on the hub. The easiest way to include a video is to use a GIF, for example hosted
 on imgur. You can then reference this GIF as an image.
 
@@ -59,7 +59,7 @@ anywhere, feel free to also include this information here.
 This section should go through step-by-step examples of how your plugin should be used.
 Where your plugin provides multiple dock widgets or functions, you should split these
 out into separate subsections for easy browsing. Include screenshots and videos
-wherever possible to elucidate your descriptions. 
+wherever possible to elucidate your descriptions.
 
 Ideally, this section should start with minimal examples for those who just want a
 quick overview of the plugin's functionality, but you should definitely link out to
@@ -72,8 +72,8 @@ for the majority of plugins. They will include instructions to pip install, and
 to install via napari itself.
 
 Most plugins can be installed out-of-the-box by just specifying the package requirements
-over in `setup.cfg`. However, if your plugin has any more complex dependencies, or 
-requires any additional preparation before (or after) installation, you should add 
+over in `setup.cfg`. However, if your plugin has any more complex dependencies, or
+requires any additional preparation before (or after) installation, you should add
 this information here.
 
 ## Getting Help

.pre-commit-config.yaml

@@ -1,12 +1,12 @@
 repos:
   - repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v4.0.1
+    rev: v4.2.0
     hooks:
       - id: check-docstring-first
       - id: end-of-file-fixer
       - id: trailing-whitespace
   - repo: https://github.com/asottile/setup-cfg-fmt
-    rev: v1.20.0
+    rev: v1.20.1
     hooks:
       - id: setup-cfg-fmt
   - repo: https://github.com/PyCQA/flake8
@@ -24,11 +24,11 @@ repos:
     hooks:
       - id: isort
   - repo: https://github.com/psf/black
-    rev: 21.11b1
+    rev: 22.3.0
     hooks:
       - id: black
   - repo: https://github.com/asottile/pyupgrade
-    rev: v2.29.1
+    rev: v2.32.0
     hooks:
       - id: pyupgrade
         args: [--py38-plus, --keep-runtime-typing]