Centralize developer tooling across components #1773
Labels
⚙️ Tooling
Improving maintainability and increasing maintainer joy : )
Comments
legoktm
added
the
⚙️ Tooling
Closed
legoktm
added a commit
that referenced
this issue
Feb 8, 2024
Both of these projects can be run centrally across all components and don't need to be installed and configured separately four times. This also identifies and fixes that bandit wasn't being run on export (though the issue it flagged was a false positive). Refs #1773.
legoktm
added a commit
that referenced
this issue
Feb 12, 2024
Both of these projects can be run centrally across all components and don't need to be installed and configured separately four times. This also identifies and fixes that bandit wasn't being run on export (though the issue it flagged was a false positive). Refs #1773.
legoktm
added a commit
that referenced
this issue
Feb 22, 2024
Run black and isort from the root and apply it unconditionally to every file in the repository. Refs #1773.
2 tasks
legoktm
added a commit
that referenced
this issue
Feb 22, 2024
Run black and isort from the root and apply it unconditionally to every file in the repository. Refs #1773.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Currently each Python component has its own black, isort, flake8, etc. We should instead have a top-level pyproject.toml + Makefile that runs all of those across every Python file in the repo. This will cut down on the number of duplicated dependencies and make it easier for CI and hopefully, developers too.
Tools that rely on being installed in the same virtualenv, like pytest and mypy should probably not be centralized, unless it actually works out fine!
The text was updated successfully, but these errors were encountered: