Python
/
ruff
mirror of https://github.com/astral-sh/ruff
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Remove language about RUF104 until that's ready/landed

This commit is contained in:
Amethyst Reese 2025-12-11 11:11:11 -08:00
parent 6672bb3e8c
commit 0f39c460e0
1 changed files with 4 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/linter.md
View File

@ -366,10 +366,9 @@ def foo():
# ruff: enable[E741, F841] # ruff: enable[E741, F841]
``` ```
If no matching "enable" comment is found, a RUF10x violation will be raised for unmatched If no matching "enable" comment is found, Ruff will also treat this as an "implicit" range.
range suppression, though Ruff will also treat this as an "implicit" range. The implicit The implicit range is defined from the starting "disable" comment, until reaching
range is defined from the starting "disable" comment, until reaching a logical scope a logical scope indented less than the starting comment:
indented less than the starting comment:
```python ```python
def foo(): def foo():
@ -384,9 +383,7 @@ foo()
``` ```
It is strongly suggested to use explicit range suppressions, in order to prevent It is strongly suggested to use explicit range suppressions, in order to prevent
accidental suppressions of violations, especially at global module scope. If implicit accidental suppressions of violations, especially at global module scope.
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.
Range suppressions cannot be used to enable or select rules that aren't already 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 selected by the project configuration or runtime flags. An "enable" comment can only