Python lint: Ruff rules for comprehensions and performance #512
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.
Fix the Python lint issues raised by:
%
ruff check --select=C4,PERF --ignore=PERF203--statistics | sort -k2
Motivation and Context
These proposed changes can make code easier to reason about or faster or both.
%
ruff rule PERF401
manual-list-comprehension (PERF401)
Derived from the Perflint linter.
Fix is sometimes available.
What it does
Checks for
for
loops that can be replaced by a list comprehension.Why is this bad?
When creating a transformed list from an existing list using a for-loop,
prefer a list comprehension. List comprehensions are more readable and
more performant.
Using the below as an example, the list comprehension is ~10% faster on
Python 3.11, and ~25% faster on Python 3.10.
Note that, as with all
perflint
rules, this is only intended as amicro-optimization, and will have a negligible impact on performance in
most cases.
Example
Use instead:
If you're appending to an existing list, use the
extend
method instead:Take care that if the original for-loop uses an assignment expression
as a conditional, such as
if match:=re.match("\d+","123")
, thenthe corresponding comprehension must wrap the assignment
expression in parentheses to avoid a syntax error.
How Has This Been Tested?
Breaking Changes
Types of changes
Checklist
Additional context
https://docs.astral.sh/ruff