Skip to content

chore(tooling): agree on common post-weld ruff rules #1403

@danceratopz

Description

@danceratopz

To keep post-Weld tooling simple, it would help to align on a shared set of ruff rules without any deviations across EEST and EELS codebases.

Common Ignored Rules (Both repos)

Rule Description Notes
D205 Missing blank line after summary Common to both (STEEL)
D203 1 blank line required before class docstring Common to both (STEEL)
D212 Multi-line docstring summary should start at the first line Common to both (STEEL)
D415 First line should end with a ".", "?", or "!" Common to both (STEEL)

execution-specs Specific Ignored Rules

Rule Description Notes
D107 Missing docstring in init EELS specific
D200 One-line docstring should fit on one line with quotes EELS specific
D400 First line should end with a period EELS specific
D401 First line should be in imperative mood EELS specific
D410 Missing blank line after last section EELS specific
D411 Missing blank line before last section EELS specific
D412 No blank lines between sections EELS specific
D413 Missing blank line after last section EELS specific (same as D410)
D414 Section should end with a period EELS specific
D416 Section names should be in the correct order EELS specific
E203 Whitespace before ':' EELS specific

execution-spec-tests Specific Ignored Rules

Rule Description Notes
C901 Function is too complex Complexity* handled differently
A005 Builtin shadowing execution-spec-tests specific
C420 Unnecessary comprehension execution-spec-tests specific

Regarding complexity: This is configured to 7 in EELS, it's the default in EEST. 7 is fine :)

Metadata

Metadata

Assignees

Labels

A-spec-toolArea: Specification Tooling—Tools for the Ethereum specification (eg. `src/ethereum_spec_tools/*`)C-featCategory: an improvement or new featureE-mediumExperience: of moderate difficultyP-medium

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions