How do I disable a Ruff rule for a block of code?

Wrap the lines in a pair of range suppression comments: `# ruff: disable[E501]` before the block and `# ruff: enable[E501]` after it. Every rule code listed on the `disable` comment is suppressed until the matching `enable` comment. The bracketed code list is required; unlike `# noqa`, range comments do not support blanket suppression of all rules.

What is the difference between

`# noqa` suppresses rules on the single line it ends. `# ruff: disable[CODE]` opens a range that stays suppressed until a matching `# ruff: enable[CODE]`, so one comment pair covers many lines. Use `# noqa` for a single violation and a `disable`/`enable` range for a contiguous block you cannot fix yet.

Why does Ruff report RUF104 on my disable comment?

RUF104 (unmatched-suppression-comment) fires when a `# ruff: disable` has no matching `# ruff: enable`. An unclosed `disable` silently suppresses every listed rule to the end of its indentation scope, which at module level is the rest of the file. Add the `# ruff: enable` comment to close the range, or the suppression covers more code than intended.

Can I suppress all Ruff rules for a block of code?

No. Range suppression comments require at least one rule code in brackets, so `# ruff: disable` with no codes is invalid and triggers RUF103. List the specific codes to suppress, for example `# ruff: disable[E501, F401]`. To silence every rule in a whole file, use the file-level `# ruff: noqa` comment instead.

How to Disable Ruff Rules for a Block of Code

by Tim Hopper · Markdown

Ruff

Ruff suppresses a rule on a single line with # noqa, but a legacy region that trips the same rule on twenty consecutive lines needs twenty comments. Range suppression comments fix this: # ruff: disable[CODE] and # ruff: enable[CODE] quarantine a contiguous block while you adopt Ruff incrementally, without touching every line or ignoring the whole file.

This works in Ruff 0.15.0 and later, where range suppression and its validation rules (RUF103, RUF104) became stable.

Wrap the Block in disable and enable Comments

Put a # ruff: disable[CODE] comment on its own line before the block and a matching # ruff: enable[CODE] after it. Ruff suppresses the listed rule for every line in between.

# ruff: disable[E501]
SQL_TEMPLATE = "SELECT id, name, email, created_at, updated_at FROM users WHERE tenant_id = %s AND status = 'active' ORDER BY created_at DESC LIMIT 100"
LOG_FORMAT = "%(asctime)s %(levelname)-8s %(name)s:%(lineno)d %(message)s request_id=%(request_id)s trace_id=%(trace_id)s"
# ruff: enable[E501]

Run the linter to confirm the block is clean:

uv run ruff check .

The two long lines no longer report E501. Any line outside the disable/enable pair still does.

Suppress Several Rules in One Range

List the codes inside the brackets, separated by commas. The enable comment must repeat the same codes to close the range.

# ruff: disable[E501, E741]
l = "SELECT id, name, email, created_at FROM accounts WHERE tenant_id = %s AND status = 'active'"
# ruff: enable[E501, E741]

Here E741 (ambiguous variable name l) and E501 (line too long) are both suppressed for the block. Range comments require at least one code, so there is no blanket form that silences every rule. A bare # ruff: disable reports RUF103 and is ignored.

Close Every Range You Open

A # ruff: disable with no matching # ruff: enable does not error out. It suppresses the listed rules to the end of the current indentation scope, which at module level is the rest of the file.

# ruff: disable[E501]
TEMPLATE = "a very long line that exceeds the configured line length limit and then some more"
# Forgetting the enable comment suppresses E501 for everything below, too.

Ruff catches this with RUF104 (unmatched-suppression-comment), which flags any disable that lacks a closing enable. Keep RUF104 enabled so an unbalanced comment fails the lint run instead of silently widening the suppressed region.

Pick the Right Suppression Scope

Match the comment to how much code the rule should ignore:

Scope	Syntax	Use when
One line	`# noqa: E501`	A single violation on one line.
A block	`# ruff: disable[E501]` … `# ruff: enable[E501]`	A contiguous region you cannot fix yet.
Whole file	`# ruff: noqa: E501`	Generated or vendored files.

The Ruff reference lists all three levels side by side.

These comments suppress the linter. To stop the formatter from reformatting a block, see how to disable the Ruff formatter for a block of code.

Learn More

Last updated on June 24, 2026

How to Deploy a uv Project to Hugging Face Spaces How to Disable the Ruff Formatter for a Block of Code

Please submit corrections and feedback...