Removing isort, causes more issues than it solves

Author: MichaelClerx

.github/workflows/tests.yml

@@ -38,11 +38,6 @@ jobs:
       run: |
         python -m flake8 pcpostprocess
 
-    - name: Check import ordering with isort
-      if: ${{ matrix.python-version == env.python-latest }}
-      run: |
-        python -m isort --verbose --check-only --diff pcpostprocess tests setup.py
-
     - name: Extract test data
       run: |
         wget https://cardiac.nottingham.ac.uk/syncropatch_export/test_data.tar.xz -P tests/

CONTRIBUTING.md

@@ -62,17 +62,6 @@ In addition to the rules checked by flake8, we try to use single quotes (`'`) fo
 
 Class, method, and argument names are in UK english.
 
-### Import ordering
-
-Import ordering is tested with [isort](https://pycqa.github.io/isort/index.html).
-
-To run locally, use
-```
-isort --check-only --verbose ./pcpostprocess ./tests/
-```
-
-Isort is configured in [pyproject.toml](./pyproject.toml) under the section `tool.isort`.
-
 ## Documentation
 
 Every method and every class should have a [docstring](https://www.python.org/dev/peps/pep-0257/) that describes in plain terms what it does, and what the expected input and output is.

pyproject.toml

@@ -48,7 +48,6 @@ test = [
     'coverage',             # For coverage testing
     'codecov>=2.1.3',       # To upload coverage reports
     'flake8>=3',            # For code style checking
-    'isort',
 ]
 
 [tools.setuptools.package-data]
@@ -66,9 +65,6 @@ include = [
     'pcpostprocess',
 ]
 
-[tool.isort]
-skip = ['_version.py']
-
 [tool.coverage.run]
 source = [
     'pcpostprocess',