[MRG] Replace flake8
linting with ruff
linting
#961
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a small change for the purposes of replacing our previous linting with
flake8
to use the fasterruff check
linting. For previous discussion on why this is a good idea, see the parts of #934 discussingruff
linting specifically (as opposed to "formatting"). This PR was forked off from that discussion. Note that this current PR is NOT about usingruff format
to change our code-formatting-style. Instead, the "linting" inruff check
is limited to error detection (such as syntax errors) and some limited PEP8 formatting violation detection. Again, see the other issue for a more exhaustive discussion of these things, including the terminology around them.Note: for anyone doing testing on an existing install, this DOES require that you will have to install the
ruff
Python package. Alternatively, you can also installruff
by re-installing the development packages the same way you originally installedflake8
, via:pip install --editable "<your_hnn_dir>[dev]"