Tracking issue for evaluating residual packages during 2023 code update

[bskinn]

In particular, the new and updated packages showing in the Retrieve filtered package list step of this workflow run:

• New Packages:

  • flake8-airflow: Requires 3.9+
  • flake8-assert-check: Requires 3.9+
  • flake8-cgx: Requires 3.9+
  • flake8-cohesion: Requires 3.9+
  • flake8-custom-indent: Exists on PyPI but is not installable (no distributions published)
  • flake8-docstrings-catnado: Python 2-only
  • flake8-errmsg: Requires 3.10+
  • flake8-get-chaining: REAL PACKAGE, posted as expected
  • flake8-has-docstring: Requires 3.10 exactly -- good test for --ignore-requires-python
  • flake8-match: Requires 3.10+
  • flake8-naming: Exists on PyPI but has no distributions
  • flake8-num-positionl-args: Requires 3.9+
  • flake8-obey-import-goat: Requires 3.9+
  • flake8-qchecker: Requires 3.10+
  • flake8-setuptools: Exists on PyPI but has no distributions
  • flake8-unused-globals: Requires 3.10 exactly

• Updated Packages:

  • flake8-Inflammatory-Jargon: Capitalization change? Leading to perpetual inclusion?
  • flake8-SQL: Capitalization change? Leading to perpetual inclusion?
  • flake8-airflow: 3.9+
  • flake8-assert-check: 3.9+
  • flake8-cgx: 3.9+
  • flake8-cohesion: 3.9+
  • flake8-docstrings-catnado: Py2 only
  • flake8-errmsg: 3.10+
  • flake8-get-chaining: real package, should post as expected?
  • flake8-has-docstring: 3.10 exactly
  • flake8-match: 3.10+
  • flake8-num-positionl-args: 3.9+
  • flake8-obey-import-goat: 3.9+
  • flake8-qchecker: 3.10+
  • flake8-tensors ???
  • flake8-trio: updated often
  • flake8-unused-globals: 3.10 exactly
  • flake8_dodgy ???
  • flake8_doubles OLD
  • flake8_formatter_vscode ???
  • flake8_ruler ACTUAL UPDATE?
  • flake8_strict OLD
  • flake8_truveris OLD
  • flake8_typechecking_import ~OLD
  • flufl.flake8 PUNCTUATION CHANGE
  • imhotep_flake8 OLD
  • kagiso_flake8 OLD

It might be a good idea to merge main into the working branch, so that the freshest copy possible of the live JSON data is in use here. But, that could turn into a forever project, chasing the newest data. As long as everything makes sense at this snapshot in time, then the tool is likely in an okay state.