Ruff v0.16.0

The next stable version of Ruff is out now.

[email protected] (Brent Westbrook)۱ مرداد ۱۴۰۵ ۴ دقیقه مطالعهمتن اصلی

Ruff v0.16.0 is available now! Install it from PyPI, or with your package manager of choice:

uv tool install ruff@latest

As a reminder: Ruff is an extremely fast Python linter and formatter, written in Rust. Ruff can be used to replace Black, Flake8 (plus dozens of plugins), isort, pydocstyle, pyupgrade, and more, all while executing tens or hundreds of times faster than any individual tool.

Migrating to v0.16 #

Ruff v0.16 has a small number of breaking changes, allowing most users to update without significant changes to code or configuration. The main exception is described below.

Better default rule set #

Ruff now enables 413 rules by default, up from 59 in previous versions.

Since Ruff's default rule set was last modified in v0.1.0, the number of rules in Ruff has grown from 708 to 968. Many of these rules catch severe issues, including syntax errors and immediate runtime errors but were not previously enabled by default. With the new rule set, Ruff will bring these issues and many others to your attention without any Ruff configuration. Even if you're already using select or extend-select, we hope that this will draw your attention to helpful rules that you previously hadn't discovered.

The full listing of enabled rules is too long to include here, but you can find it on our new Default Rules page in the documentation. A few of the highlights include rules from the popular flake8-bugbear (

) and pyupgrade (

UP

) linters, as well as rules from our own

RUF

category.

Note that this is primarily an expansion, but 18 of the more opinionated pycodestyle (

) and pyflakes (

) rules have been removed from the default set:

E401

E402

E701

E702

E703

E711

E712

E713

E714

E721

E731

E741

E742

E743

F403

F405

F406

, and

F722

If you want to revert to the old default set, you can easily

select

the old rules with this configuration:

[lint]
select = ["E4", "E7", "E9", "F"]

We view this work as closely tied to our longstanding goal of rule recategorization, so look forward to upcoming developments in this area.

New features in v0.16 #

Ruff v0.16 also includes several newly stabilized features that are highlighted below.

Markdown code block formatting #

Ruff can now format Python code blocks embedded in Markdown files.

In these files, Ruff v0.16 will format fenced code blocks with a

python

py

python3

py3

pyi

, or

pycon

info string.

pyi

blocks are formatted like stub files,

pycon

blocks as REPL sessions, and the others use normal Python file formatting. For example:

# README

Here's an example:

```py
import ruff

ruff_binary = (
    ruff.find_ruff_bin()
)


will be reformatted when running

ruff format


:![Ruff formatter output showing a Markdown code block that would be reformatted](https://api.tech-feed.ir/media/articles/2026/10/5abf443cfa73dbee28e71ecb.webp)

This can also be used to format [Quarto](https://quarto.org/) notebooks because Ruff still
recognizes the language when surrounded by curly braces (e.g.

). Note that you may need to configure your extension mapping if your Quarto files use the

.qmd

extension.

If you need to suppress formatting, you have several options. If you want the suppression comments to appear in the code block, you can use normal

fmt: off

and

fmt: on

comments within the code block itself, or you can use similar HTML comments to disable formatting for a whole region of the document:

# README

<!-- fmt: off -->

```py
x =      "this will be suppressed"


To suppress Markdown formatting entirely, you can use the normal
[`extend-exclude`](https://docs.astral.sh/ruff/settings/#extend-exclude) setting to exclude all
Markdown files with a glob like

*.md


.

See the [full documentation](https://docs.astral.sh/ruff/formatter/#markdown-code-formatting) for
more details.

### `ruff: ignore` comments offer new suppression features [#](https://astral.sh#ruff-ignore-comments-offer-new-suppression-features)

Ruff now has its own suppression comment format that can be used on its own line.

In v0.15, the Ruff linter gained a range suppression mechanism through paired

ruff: disable

and

ruff: enable


comments, much like the

fmt: off

and

fmt: on


pair described above:

ruff: disable[N803]

def foo( legacyArg1, legacyArg2, legacyArg3, legacyArg4, ): ...

ruff: enable[N803]


Ruff v0.16 builds on this to add two additional

ruff


suppression comments.

ruff: ignore


can be
used to suppress a diagnostic on the same line, like

noqa


, or on the following logical line:

import math # ruff: ignore[F401]

ruff: ignore[N803]

def foo( legacyArg1, legacyArg2, legacyArg3, legacyArg4, ): ...


In this case, the logical line spans the whole function header (from

def


to the colon), so the

ruff: ignore


suppresses all of the same
[`N803`](https://docs.astral.sh/ruff/rules/invalid-argument-name/) diagnostics as the

disable

enable


pair above.

ruff: file-ignore


comments can be used to suppress diagnostics for the entire file, just like

ruff: noqa


comments:

ruff: file-ignore[F401] Allow unused imports in this file

import foo import bar import baz


As this example also shows, each of these comment kinds can have an associated "reason" explaining
why they were added, in this case

Allow unused imports in this file

ruff: ignore


comments can be added automatically with the new

--add-ignore


CLI flag, and in
[preview](https://docs.astral.sh/ruff/preview/), all of these

ruff


suppression comments support rule names instead of codes:

❯ echo 'import math' > try.py ❯ uvx ruff@latest check --preview --add-ignore try.py Added 1 ignore comment. ❯ cat try.py import math # ruff: ignore[unused-import]


You can find the full specification for all of these comments in the
[documentation](https://docs.astral.sh/ruff/linter/#comments).

### Fixes are now shown in `check` and `format --check` output [#](https://astral.sh#fixes-are-now-shown-in-check-and-format-check-output)

Ruff now shows the diff for linter and formatter fixes when rendering diagnostics.

Both the

check

and

format


subcommands have long supported the

--diff


flag for showing the
changes introduced by applying fixes with

check --fix

or

format


, but this was separate from the
normal output and suppressed the accompanying explanatory diagnostics. In v0.16, available fixes are
now shown as part of the default

full


output format, rendered below the

help


subdiagnostic:![Ruff check output showing the diff for an unused-import fix](https://api.tech-feed.ir/media/articles/2026/10/39a80224a5f1d3a96268f361.webp)

The same is true for

format --check


. Given the following input:

example.py

if True: pass elif False: pass


The formatter produces:

![Ruff formatter output showing the diff for an unformatted file](https://api.tech-feed.ir/media/articles/2026/10/17a362ccbf45cfaec366e8c3.webp)

format --check


also now supports the full selection of output formats supported by the linter. You
can use this to obtain machine-readable JSON output or produce the formats expected by GitHub and
GitLab to render annotations in CI, as just a couple of examples. See the CLI help or
[documentation](https://docs.astral.sh/ruff/settings/#output-format) for the full list of supported
formats.

One final note on output formats is that there is a small breaking change to the JSON output in
v0.16. The

filename

location

end_location

fix.edits[].location


, and

fix.edits[].end_location


fields may now be

null


rather than defaulting to the empty string and
row 1, column 1, respectively. This should affect very few of Ruff's existing diagnostics but better
reflects the internal diagnostic representation and may become more common in future rules.

## Rule stabilizations [#](https://astral.sh#rule-stabilizations)

The following rules have been stabilized and are no longer in
[preview](https://docs.astral.sh/ruff/preview/):

- [`airflow3-incompatible-function-signature`](https://docs.astral.sh/ruff/rules/airflow3-incompatible-function-signature)
  (`AIR303`)
- [`missing-copyright-notice`](https://docs.astral.sh/ruff/rules/missing-copyright-notice)
  (`CPY001`)
- [`unnecessary-from-float`](https://docs.astral.sh/ruff/rules/unnecessary-from-float) (`FURB164`)
- [`sorted-min-max`](https://docs.astral.sh/ruff/rules/sorted-min-max) (`FURB192`)
- [`implicit-string-concatenation-in-collection-literal`](https://docs.astral.sh/ruff/rules/implicit-string-concatenation-in-collection-literal)
  (`ISC004`)
- [`log-exception-outside-except-handler`](https://docs.astral.sh/ruff/rules/log-exception-outside-except-handler)
  (`LOG004`)
- [`invalid-bool-return-type`](https://docs.astral.sh/ruff/rules/invalid-bool-return-type)
  (`PLE0304`)
- [`too-many-positional-arguments`](https://docs.astral.sh/ruff/rules/too-many-positional-arguments)
  (`PLR0917`)
- [`stop-iteration-return`](https://docs.astral.sh/ruff/rules/stop-iteration-return) (`PLR1708`)
- [`none-not-at-end-of-union`](https://docs.astral.sh/ruff/rules/none-not-at-end-of-union)
  (`RUF036`)
- [`access-annotations-from-class-dict`](https://docs.astral.sh/ruff/rules/access-annotations-from-class-dict)
  (`RUF063`)
- [`duplicate-entry-in-dunder-all`](https://docs.astral.sh/ruff/rules/duplicate-entry-in-dunder-all)
  (`RUF068`)

## Other behavior stabilizations [#](https://astral.sh#other-behavior-stabilizations)

This release also stabilizes some additional behavior, previously only available in
[preview mode](https://docs.astral.sh/ruff/preview/):

- [`blind-except`](https://docs.astral.sh/ruff/rules/blind-except) (`BLE001`) is now suppressed when
  the exception is logged via `logging` methods other than `critical`, `error` and `exception`.
- [`future-required-type-annotation`](https://docs.astral.sh/ruff/rules/future-required-type-annotation)
  (`FA102`) now checks for additional [PEP 585](https://peps.python.org/pep-0585/)-compatible APIs, such as those from
  `collections.abc`.
- [`f-string-in-get-text-func-call`](https://docs.astral.sh/ruff/rules/f-string-in-get-text-func-call)
  (`INT001`),
  [`format-in-get-text-func-call`](https://docs.astral.sh/ruff/rules/format-in-get-text-func-call)
  (`INT002`), and
  [`printf-in-get-text-func-call`](https://docs.astral.sh/ruff/rules/printf-in-get-text-func-call)
  (`INT003`) now check for additional common ways of using the `gettext` module, such as assigning
  it to `builtins._`.
- [`suspicious-url-open-usage`](https://docs.astral.sh/ruff/rules/suspicious-url-open-usage)
  (`S310`) now resolves local string literal bindings to avoid more false positives.
- [`snmp-insecure-version`](https://docs.astral.sh/ruff/rules/snmp-insecure-version) (`S508`) and
  [`snmp-weak-cryptography`](https://docs.astral.sh/ruff/rules/snmp-weak-cryptography) (`S509`) now
  support the recommended API from newer versions of PySNMP.
- [`typing-text-str-alias`](https://docs.astral.sh/ruff/rules/typing-text-str-alias) (`UP019`) now
  recognizes `typing_extensions.Text` in addition to `typing.Text`.

## Thank you! [#](https://astral.sh#thank-you)

Thank you to everyone who provided feedback regarding the changes included in Ruff's
[preview mode](https://docs.astral.sh/ruff/settings/#preview) and to our contributors. It's an honor
building Ruff with you!

View the full changelog on [GitHub](https://github.com/astral-sh/ruff/releases/tag/0.16.0).

Read more about [Astral](https://astral.sh/about) — the company behind Ruff.

*Thanks to Zanie Blue, David Peter, Micha Reiser, and Alex Waygood who contributed to this blog
post.*

#Python

منتشرشده در

Astral

خواندن در منبع