Using ruff for linting #04 #82
Merged
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.
Update ruff lint select rules. This pull request includes follow-up modifications and refinements related to the integration of Ruff, a linter for Python. Updated rules in
pyproject.toml
:S
– Security issues (viaflake8-bandit
), such as unsafe use of functions likeeval
,assert
, etc.E
– PEP 8 style errors (viapycodestyle
)A
– Built-in shadowing (viaflake8-builtins
) to avoid overwriting Python built-in namesN
– Naming conventions (e.g., snake_case for functions, PascalCase for classes)I
– Import sorting (viaisort
)B
– Bug and bad practice detection (viaflake8-bugbear
)YTT
– Outdated Python compatibility checks (viaflake8-2020
)FLY
– f-string modernization (viaflynt
)PIE
– Miscellaneous improvements and best practices (viaflake8-pie
)