This pins the current dev tool versions, so that they are repeatable.
Note that there is no "requirements.txt" because there are currently no runtime requirements, only development/linting/testing.
This is not the most "modern" way of defining those requirements (pyproject.toml), but is the simplest, and does not interfere with the current package publishing workflow.
This pins the current dev tool versions, so that they are repeatable.
Note that there is no "requirements.txt" because there are currently no runtime requirements, only development/linting/testing.
This is not the most "modern" way of defining those requirements (
pyproject.toml
), but is the simplest, and does not interfere with the current package publishing workflow.