From 0f39c460e06b143966c7153af573823033a3e3b8 Mon Sep 17 00:00:00 2001 From: Amethyst Reese Date: Thu, 11 Dec 2025 11:11:11 -0800 Subject: [PATCH] Remove language about RUF104 until that's ready/landed --- docs/linter.md | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/docs/linter.md b/docs/linter.md index 5e36777a8e..6644d54f34 100644 --- a/docs/linter.md +++ b/docs/linter.md @@ -366,10 +366,9 @@ def foo(): # ruff: enable[E741, F841] ``` -If no matching "enable" comment is found, a RUF10x violation will be raised for unmatched -range suppression, though Ruff will also treat this as an "implicit" range. The implicit -range is defined from the starting "disable" comment, until reaching a logical scope -indented less than the starting comment: +If no matching "enable" comment is found, Ruff will also treat this as an "implicit" range. +The implicit range is defined from the starting "disable" comment, until reaching +a logical scope indented less than the starting comment: ```python def foo(): @@ -384,9 +383,7 @@ foo() ``` It is strongly suggested to use explicit range suppressions, in order to prevent -accidental suppressions of violations, especially at global module scope. If implicit -range suppressions are desired, the RUF10x lint can be disabled, or an inline `noqa` -suppression can be added to the end of the "disable" comment. +accidental suppressions of violations, especially at global module scope. Range suppressions cannot be used to enable or select rules that aren't already selected by the project configuration or runtime flags. An "enable" comment can only