Skip to main content

ruff-odoo

PyPI CI Docs

ruff-odoo is Vauxoo's fork of Ruff, shipping every upstream linter and formatter rule plus the OD and OAPP rule groups, ported from pylint-odoo and odoo-pre-commit-hooks.

This file covers what differs from upstream Ruff for anyone installing or building the fork: why it exists at all, the command name, the packaging, and the version scheme.

Why this exists

Vauxoo's Odoo checks used to live in pylint-odoo (a Pylint plugin) and odoo-pre-commit-hooks, running next to the autofixing tools already present in the pre-commit stack. Three problems pushed us to port those checks into Ruff instead, and none of them was something a patch to those projects could have fixed.

Autofixes corrupted each other. Every tool rewrote the file on its own, with no idea of what the others had done to it. A fix applied by one hook routinely invalidated a fix another hook had just applied, or uncovered a violation that only became reachable after the first rewrite. So the run ended dirty, the command had to be run a second time, and that run pulled in yet another fix. Getting a repository to a fixed point — a run that proposes no changes — commonly took three or four passes of the same command. That is confusing on a developer machine and simply broken in CI, where there is one run and a dirty tree is a failure.

Ruff does that iteration internally: it lints, applies every non-overlapping fix, re-parses the result, and repeats until the file stops changing, discarding any fix that would have introduced a syntax error. One invocation, one stable file.

Pylint has no autofixes. Pylint only reports. Any check we also wanted fixed automatically had to be written twice — once as a Pylint checker that reports it and once as a separate fixer that rewrites it — with two sets of tests, two notions of what the pattern is, and no guarantee the two stayed in agreement as they were maintained. In Ruff a fix is attached to the diagnostic that produced it, so the rule that finds a problem is the same code that repairs it, and its fixture covers both.

Speed, which mattered more than anything else. A linter is only run as often as it is cheap to run. Pylint infers types through astroid, and a stack of separate hooks pays for a process start and a fresh parse of every file per tool. Ruff parses each file once, in Rust, in parallel across cores, and caches unchanged files between runs — fast enough to run on save and on every commit rather than only in CI, which is what makes the rules actually shape the code being written instead of being discovered at review time.

Why a fork, and not a separate repository

The obvious alternative was to keep the Odoo rules in their own project and just depend on Ruff. It does not work, for reasons that are structural rather than incidental:

  • Ruff has no plugin system. Rules are compiled into the binary; there is no dynamic loading, no stable ABI, and no "register a rule" entry point to call from the outside. That is a deliberate design choice upstream — it is part of why a single static binary can dispatch rules with no per-rule overhead — not a gap waiting to be filled.
  • A rule is not self-contained. Adding one touches files that upstream owns: the code-to-rule map in codes.rs, the linter enum in registry.rs, the dispatch inside the AST visitor in checkers/ast/analyze/, the settings struct behind lint.odoo, and the generated JSON schema and docs. There is no seam an external crate could attach to.
  • The internal crates are not a public API. ruff_linter describes itself as "an internal component crate of Ruff": it is versioned with the binary and refactored freely. A separate project built on it would break on close to every upstream release, which is a worse maintenance burden than a rebase.
  • A second tool would recreate the original problem. Even with all of the above solved, shipping the Odoo rules as a second binary means a second process, a second parse, a second fix pass over the same file, a second configuration file, and a second suppression syntax. The whole point is that the Odoo rules run in the same pass as everything else: one command, one AST, one --fix, one # noqa, one cache, one pyproject.toml.

The cost of this choice is having to rebase onto upstream Ruff, and that is accepted knowingly. The fork is arranged to keep that cost low: the Odoo rules live in their own directory, upstream files are touched as little as possible, and the ruff crate and its binary are left untouched behind a thin wrapper crate.

The ruff-odoo command

The published command is ruff-odoo, not ruff. It is the exact same CLI, only under a name that cannot collide with an upstream ruff installation, so both can live in the same environment:

$ ruff-odoo check   # Lint all files in the current directory.
$ ruff-odoo format  # Format all files in the current directory.

The Python module is ruff_odoo, so the CLI is also reachable without the console script:

$ python -m ruff_odoo check

Installation

The package is published to PyPI as ruff-odoo. It is not distributed through Homebrew, conda, Docker, or the standalone astral.sh installers — those channels ship upstream Ruff only.

$ # Run it without installing.
$ uvx ruff-odoo check

$ # Install it globally.
$ uv tool install ruff-odoo@latest

$ # Or add it to your project.
$ uv add --dev ruff-odoo

$ # With pip.
$ pip install ruff-odoo

Installing ruff-odoo alongside the upstream ruff package is supported, even in the same environment: ruff-odoo owns the ruff-odoo entry point and never touches ruff.

pre-commit

Use the mirror repository, which installs the prebuilt wheels:

repos:
  - repo: https://github.com/vauxoo/ruff-pre-commit
    # Use the latest release tag; see the version scheme below.
    rev: 0.17.0.35
    hooks:
      - id: ruff-check
      - id: ruff-format

The hook ids match astral-sh/ruff-pre-commit, so switching between upstream and this fork means changing only repo and rev.

This repository also defines the hooks directly (see .pre-commit-hooks.yaml), but pointing repo at it builds Ruff from source with maturin on every environment creation, which is slow and requires a Rust toolchain. Prefer the mirror.

Python code in Odoo XML data files

ruff-odoo check and ruff-odoo format also handle the Python that Odoo keeps in XML: the code field of every ir.cron and ir.actions.server record, and of every base.automation record, which up to 16.0 carries the code of the server action it delegates to. It works like the Markdown support of ruff format: the code is taken out of the document, checked or formatted as Python, and, for format, written back in place, leaving the rest of the file untouched.

XML files are opted in, never discovered on their own. Pass them explicitly, as pre-commit does, or add them to extend-include:

[tool.ruff]
extend-include = ["*.xml"]

With pre-commit, add xml to the files the hooks receive:

      - id: ruff-check
        types_or: [python, pyi, jupyter, xml]
      - id: ruff-format
        types_or: [python, pyi, jupyter, xml]

What is checked is exactly what Odoo runs, safe_eval(code.strip(), ..., mode="exec"):

  • Entities (<, &, …) and CDATA sections are decoded first, and every diagnostic is reported at its line and column in the XML file.
  • A record whose state is set to anything other than code is skipped, since Odoo never runs its code. A record that does not set state is checked: a scheduled action defaults to code, and a record that only overrides the code of an existing action keeps the state that action has. A code field filled from an eval, ref, file or search attribute is skipped too.
  • The names Odoo puts in the evaluation context (env, model, record, records, log, time, datetime, UserError, Command, …, and an AI tool's ai and arguments) count as builtins, so they are not reported as undefined. They are the names of the configured lint.odoo.odoo-version, from 12.0 to 20.0: UserError only from 14.0, Command from 15.0, _logger and payload from 17.0. A version without a set of its own uses the closest one before it, and the newest set applies when no version is configured.
  • Rules about the file rather than the code are turned off for the fields: D100, CPY001, I002, INP001, N999, A005, EXE001, EXE002 and ODC8501.
  • The OD rules read the code the way they read a method of the record's model: env is self.env, and model, record and records are self, a recordset of the model the record's model_id refers to. So env.cr.execute("..." % value) is ODE8103, env.cr.commit() is ODE8102, records.read_group(...) is ODW8502 on 19.0, records.name_get() is ODE9503, and the translation rules recommend env._ (and stay silent before 18.0, where a field has no translation function). env.cr counts as a cursor in Python files too, where it is the env of a post_init_hook(env). SLF001 lets model._cron_x() through, as it lets self._x() through in a method.
  • ODW8163 (no-search-all) goes further in a field than in a method: a search or search_read without a limit on a model known to grow is reported whatever its domain (unless it pins id with = or in), since the field runs in one transaction and holds every row it matched and wrote until it ends. A cron posting every draft journal entry of the day that way kept deadlocking against Odoo's own auto-post cron. The model of model, record and records is compared through its XML id (account.model_account_move), with dots and underscores taken as equal.
  • A body indented under its <field> tag is a syntax error when it holds several statements (Odoo strips the first line only) and is reported as one. A single compound statement indented that way runs, and is checked and formatted without the extra indentation, which format then puts back. The line width is the code's own, the same for format and E501, without that indentation. When the indentation cannot be removed without changing the program (a multi-line string inside the body), the field is checked as it is and left unformatted.
  • check --fix never rewrites an XML file; format is the only tool that does. It keeps the document's line endings, whatever line-ending says, and leaves alone a field that does not parse: the syntax error is reported by check, not by format.
  • Some files are skipped without a diagnostic: XML that is not well-formed, a field that uses an entity declared in a DOCTYPE, and XML that is not UTF-8. --add-noqa does not handle XML; write the # noqa comments in the field by hand.

Version scheme

Fork releases use four components, x.y.z.w:

  • x.y.z is the upstream Ruff release this fork is based on (for example 0.16.2).
  • w counts the fork's own releases, independently of that upstream base.

So 0.16.2.4 is the fourth Vauxoo release, built on upstream Ruff 0.16.2. When the fork is synced onto a newer upstream, x.y.z follows it and w carries over untouched: syncing 0.16.2.4 onto upstream 0.16.3 gives 0.16.3.4, and the next release is 0.16.3.5. The counter never restarts, so a fork version is never reused and never goes backwards.

The version lives in [project] version of the root pyproject.toml and is bumped by bump2version (see .bumpversion.cfg), which also creates the release tag. Tags are the bare version with no prefix (0.16.2.4, not v0.16.2.4); pushing one triggers the PyPI release workflow. Because every fork tag has four components, it can never be confused with one of upstream's three-component tags.

Cargo cannot express a four-component version, so crates/ruff_odoo/Cargo.toml keeps the three-component x.y.z and crates/ruff/build.rs reads the real version out of pyproject.toml at build time, exposing it as RUFF_ODOO_VERSION. A build made outside a checkout of this repository falls back to the Cargo version.

Reporting the version

--version prints the bare version and nothing else:

$ ruff-odoo --version
ruff-odoo 0.17.0.35

It stays bare on purpose: tools that shell out to the binary (ruff-lsp, for one) parse that output as a PEP 440 version and fail on anything appended to it.

The version subcommand is the verbose one. It adds the number of commits since the release tag and the commit the binary was built from:

$ ruff-odoo version
ruff-odoo 0.17.0.35+3 (b45cfcb38 2026-08-15)

The leading name is the binary that was actually invoked, so a locally built ruff dev binary introduces itself as ruff. A release build sitting exactly on its tag has no +N suffix.

For machine-readable output, ask for JSON:

$ ruff-odoo version --output-format json
{
  "version": "0.17.0.35",
  "commit_info": {
    "short_commit_hash": "b45cfcb38",
    "commit_hash": "b45cfcb38d111d9f446b195125290a19e4cf8a4e",
    "commit_date": "2026-08-15",
    "last_tag": "0.17.0.35",
    "commits_since_last_tag": 3
  }
}

Building from source

The ruff-odoo binary is a thin wrapper crate (crates/ruff_odoo) around the untouched upstream ruff crate; the only differences are the displayed command name and the error prefix. Keeping the ruff crate and its binary unmodified is what keeps rebases onto upstream cheap.

Both binaries build from this checkout, and either one is fine for development:

cargo run --bin ruff-odoo -- check path/to/file.py
cargo run --bin ruff -- check path/to/file.py

See AGENTS.md for the full development workflow, and CONTRIBUTING.md for upstream's.

Metadata

Release files for ruff-odoo 0.17.0.35

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ruff-odoo 0.17.0.35
File Size Uploaded Provenance Actions
ruff_odoo-0.17.0.35.tar.gz 5.5 MB Without provenance Details for ruff_odoo-0.17.0.35.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for ruff-odoo 0.17.0.35
File Actions
ruff_odoo-0.17.0.35-py3-none-win_arm64.whl Python 3 none Windows ARM64 Details for ruff_odoo-0.17.0.35-py3-none-win_arm64.whl
ruff_odoo-0.17.0.35-py3-none-win_amd64.whl Python 3 none Windows x86-64 Details for ruff_odoo-0.17.0.35-py3-none-win_amd64.whl
ruff_odoo-0.17.0.35-py3-none-win32.whl Python 3 none Windows x86-32 Details for ruff_odoo-0.17.0.35-py3-none-win32.whl
ruff_odoo-0.17.0.35-py3-none-musllinux_1_2_x86_64.whl Python 3 none Linux musl 1.2+ x86-64 Details for ruff_odoo-0.17.0.35-py3-none-musllinux_1_2_x86_64.whl
ruff_odoo-0.17.0.35-py3-none-musllinux_1_2_i686.whl Python 3 none Linux musl 1.2+ x86-32 Details for ruff_odoo-0.17.0.35-py3-none-musllinux_1_2_i686.whl
ruff_odoo-0.17.0.35-py3-none-musllinux_1_2_armv7l.whl Python 3 none Linux musl 1.2+ ARMv7l Details for ruff_odoo-0.17.0.35-py3-none-musllinux_1_2_armv7l.whl
ruff_odoo-0.17.0.35-py3-none-musllinux_1_2_aarch64.whl Python 3 none Linux musl 1.2+ ARM64 Details for ruff_odoo-0.17.0.35-py3-none-musllinux_1_2_aarch64.whl
ruff_odoo-0.17.0.35-py3-none-manylinux_2_31_riscv64.whl Python 3 none Linux glibc 2.31+ RISC-V 64 Details for ruff_odoo-0.17.0.35-py3-none-manylinux_2_31_riscv64.whl
ruff_odoo-0.17.0.35-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl Python 3 none Linux glibc 2.17+ x86-64 Details for ruff_odoo-0.17.0.35-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
ruff_odoo-0.17.0.35-py3-none-manylinux_2_17_s390x.manylinux2014_s390x.whl Python 3 none Linux glibc 2.17+ IBM System/390x Details for ruff_odoo-0.17.0.35-py3-none-manylinux_2_17_s390x.manylinux2014_s390x.whl
ruff_odoo-0.17.0.35-py3-none-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl Python 3 none Linux glibc 2.17+ PowerPC 64-le Details for ruff_odoo-0.17.0.35-py3-none-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl
ruff_odoo-0.17.0.35-py3-none-manylinux_2_17_i686.manylinux2014_i686.whl Python 3 none Linux glibc 2.17+ x86-32 Details for ruff_odoo-0.17.0.35-py3-none-manylinux_2_17_i686.manylinux2014_i686.whl
ruff_odoo-0.17.0.35-py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.whl Python 3 none Linux glibc 2.17+ ARMv7l Details for ruff_odoo-0.17.0.35-py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.whl
ruff_odoo-0.17.0.35-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl Python 3 none Linux glibc 2.17+ ARM64 Details for ruff_odoo-0.17.0.35-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
ruff_odoo-0.17.0.35-py3-none-macosx_11_0_arm64.whl Python 3 none macOS 11.0+ ARM64 Details for ruff_odoo-0.17.0.35-py3-none-macosx_11_0_arm64.whl
ruff_odoo-0.17.0.35-py3-none-macosx_10_12_x86_64.whl Python 3 none macOS 10.12+ x86-64 Details for ruff_odoo-0.17.0.35-py3-none-macosx_10_12_x86_64.whl
ruff_odoo-0.17.0.35-py3-none-linux_armv6l.whl Python 3 none linux armv6l Details for ruff_odoo-0.17.0.35-py3-none-linux_armv6l.whl

Total release size: 188.3 MB

Release files / ruff_odoo-0.17.0.35.tar.gz

Download URL ruff_odoo-0.17.0.35.tar.gz
Size 5.5 MB
Tags Source
SHA-256 checksum
How to use checksums
913899c9e8fd1a186695bd16ba0a9c1d3249a685a45031ae6818e41da90a9413
BLAKE2b-256 checksum
How to use checksums
5ea8699bdbce9bc10c249d42cd6fd5594bb98fc9b4bde5b7a26febdfd69cf8fe
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / ruff_odoo-0.17.0.35-py3-none-win_arm64.whl

Download URL ruff_odoo-0.17.0.35-py3-none-win_arm64.whl
Size 10.8 MB
Tags Python 3 Windows ARM64
SHA-256 checksum
How to use checksums
e91d4aa390be230046871c967e7b18d2370c6f2d933641541e8056e97853d163
BLAKE2b-256 checksum
How to use checksums
1900a2b1bc153cb6f7385471479b671048f03c41d871d15307c04cea164202cd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / ruff_odoo-0.17.0.35-py3-none-win_amd64.whl

Download URL ruff_odoo-0.17.0.35-py3-none-win_amd64.whl
Size 10.9 MB
Tags Python 3 Windows x86-64
SHA-256 checksum
How to use checksums
4d7add7f77fb06cad7521c528eec4d252b7f161937264a76e6f0a397763d6101
BLAKE2b-256 checksum
How to use checksums
43374905d1b321a644fa87676f4c0eb4e0ba9c16db176882bb84db0ae4a1266a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / ruff_odoo-0.17.0.35-py3-none-win32.whl

Download URL ruff_odoo-0.17.0.35-py3-none-win32.whl
Size 10.6 MB
Tags Python 3 Windows x86-32
SHA-256 checksum
How to use checksums
805bdb2a64cacac97c51937e8e70b274febece5ceb826a52f4759b55ad3c0c54
BLAKE2b-256 checksum
How to use checksums
65e2bbe2e4b0c0a865d318b7e3723607833e3496f75c4d133e7a5ae06959438a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / ruff_odoo-0.17.0.35-py3-none-musllinux_1_2_x86_64.whl

Download URL ruff_odoo-0.17.0.35-py3-none-musllinux_1_2_x86_64.whl
Size 11.2 MB
Tags Linux musl 1.2+ x86-64 Python 3
SHA-256 checksum
How to use checksums
59adb9e2cd62b2fe6a32aab89198bd6f1b184e027ba3ca7f2b22bee6054f7cca
BLAKE2b-256 checksum
How to use checksums
5731bdee3480cdc96a19e02c883f5206ea7317c79c2313197401203552f3b525
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / ruff_odoo-0.17.0.35-py3-none-musllinux_1_2_i686.whl

Download URL ruff_odoo-0.17.0.35-py3-none-musllinux_1_2_i686.whl
Size 10.8 MB
Tags Linux musl 1.2+ x86-32 Python 3
SHA-256 checksum
How to use checksums
cf6c0e00cfb4a6f4e08b1a2314cae45d5b90897215cedbd8ce99e9832e64192e
BLAKE2b-256 checksum
How to use checksums
72c53709b24caf0618bd77f99c0b50856003112101bf1528076ebd5621fc0a4e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / ruff_odoo-0.17.0.35-py3-none-musllinux_1_2_armv7l.whl

Download URL ruff_odoo-0.17.0.35-py3-none-musllinux_1_2_armv7l.whl
Size 10.3 MB
Tags Linux musl 1.2+ ARMv7l Python 3
SHA-256 checksum
How to use checksums
15b15bba5bd24d2276010cbd2464ffbac175fec1cf21c8b66a86d70b1c892e05
BLAKE2b-256 checksum
How to use checksums
9a626b62dc8e62d2544b86add49aa4412662bc3b2155ef10dbf6db58ca1f9bf7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / ruff_odoo-0.17.0.35-py3-none-musllinux_1_2_aarch64.whl

Download URL ruff_odoo-0.17.0.35-py3-none-musllinux_1_2_aarch64.whl
Size 10.5 MB
Tags Linux musl 1.2+ ARM64 Python 3
SHA-256 checksum
How to use checksums
eb612c4399e1e363694f0f8c2a405ff93b64942b9dd2abac4b3d851c52b833e8
BLAKE2b-256 checksum
How to use checksums
a53070dc8f2aff486bea673700daa25e887780f9142657dd5b97d61d49e3ec12
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / ruff_odoo-0.17.0.35-py3-none-manylinux_2_31_riscv64.whl

Download URL ruff_odoo-0.17.0.35-py3-none-manylinux_2_31_riscv64.whl
Size 10.9 MB
Tags Linux glibc 2.31+ RISC-V 64 Python 3
SHA-256 checksum
How to use checksums
0d9a6749bc420ffd81bd6c65f2b9ea4e666db802119ccaf7ad8f05a85a72398e
BLAKE2b-256 checksum
How to use checksums
98863606d02463508ba75295c2ca0368ddd8e6b0dfae2508231ded3cb2ff57d3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / ruff_odoo-0.17.0.35-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL ruff_odoo-0.17.0.35-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 10.7 MB
Tags Linux glibc 2.17+ x86-64 Python 3
SHA-256 checksum
How to use checksums
f922fbddb45a00dc5bd5e074704646825b96330757685adece0662a765ee9893
BLAKE2b-256 checksum
How to use checksums
b61ca97c7e0795a6cae030b95cf06b2e21ae63e0b15e5522b89d71d14f56774a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / ruff_odoo-0.17.0.35-py3-none-manylinux_2_17_s390x.manylinux2014_s390x.whl

Download URL ruff_odoo-0.17.0.35-py3-none-manylinux_2_17_s390x.manylinux2014_s390x.whl
Size 11.4 MB
Tags Linux glibc 2.17+ IBM System/390x Python 3
SHA-256 checksum
How to use checksums
532aba6889f3298bb91a9d871f971b025bff16999befdaa5f4e40cf48824feac
BLAKE2b-256 checksum
How to use checksums
188f489a6fbb2c5b303710fb5c2fc626c46cef8232c47dca4b97c15484007b23
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / ruff_odoo-0.17.0.35-py3-none-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl

Download URL ruff_odoo-0.17.0.35-py3-none-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl
Size 11.8 MB
Tags Linux glibc 2.17+ PowerPC 64-le Python 3
SHA-256 checksum
How to use checksums
94c949230bdf8c8d2265c546e9cdc7459ce45d2f70cc68e93d8a684feea55ca2
BLAKE2b-256 checksum
How to use checksums
096dc1f857edac536246e9af29b48831506030fae18a0abb446ce57e3e55857b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / ruff_odoo-0.17.0.35-py3-none-manylinux_2_17_i686.manylinux2014_i686.whl

Download URL ruff_odoo-0.17.0.35-py3-none-manylinux_2_17_i686.manylinux2014_i686.whl
Size 11.1 MB
Tags Linux glibc 2.17+ x86-32 Python 3
SHA-256 checksum
How to use checksums
8f173bc6b674ad660fc4f0cd91631744a438ee9e668384df14793d7e8c9d195a
BLAKE2b-256 checksum
How to use checksums
52ab2736e69abfb72a9f2004e86a082d837adf4748503c2ba2c36a8804c31d59
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / ruff_odoo-0.17.0.35-py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.whl

Download URL ruff_odoo-0.17.0.35-py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.whl
Size 10.3 MB
Tags Linux glibc 2.17+ ARMv7l Python 3
SHA-256 checksum
How to use checksums
1fe5643d920ebde3a6e9ae1a22781dccc7603ed46457c655fb42c7f163491917
BLAKE2b-256 checksum
How to use checksums
21b2e863ac6353cc4bbd5ede4a42bd0bb2a5d37da3158b799bbc76cedc5cb854
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / ruff_odoo-0.17.0.35-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL ruff_odoo-0.17.0.35-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 10.3 MB
Tags Linux glibc 2.17+ ARM64 Python 3
SHA-256 checksum
How to use checksums
8961a2f7d7b7256b4a4d190f30b7ff11c62d971981bf66abc392fee491c35e45
BLAKE2b-256 checksum
How to use checksums
eedf7abf0b7fafd25fee7964814aac031544247af2f91145d40727414883a8bf
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / ruff_odoo-0.17.0.35-py3-none-macosx_11_0_arm64.whl

Download URL ruff_odoo-0.17.0.35-py3-none-macosx_11_0_arm64.whl
Size 10.1 MB
Tags Python 3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
f0b1df0174ea19ba956d2f9a6b73218a8df4ebe770f67f429e72fd45fb938f90
BLAKE2b-256 checksum
How to use checksums
3d205003b1849d8027fc8a6934da6f7aad53af20f2b521b40a417dd06b4ed0cd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / ruff_odoo-0.17.0.35-py3-none-macosx_10_12_x86_64.whl

Download URL ruff_odoo-0.17.0.35-py3-none-macosx_10_12_x86_64.whl
Size 10.8 MB
Tags Python 3 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
45bb630675fbe8112034131f3292d122ad0193b8b9f432e1be7744771b766913
BLAKE2b-256 checksum
How to use checksums
2512e706fa4af0935628718a2dfd5711c4f256d579495c56a0a92d64e9935019
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / ruff_odoo-0.17.0.35-py3-none-linux_armv6l.whl

Download URL ruff_odoo-0.17.0.35-py3-none-linux_armv6l.whl
Size 10.5 MB
Tags Python 3 linux armv6l
SHA-256 checksum
How to use checksums
02ae760ce35f9acb5d65ccb510e3ec9bbfc04abff71a4f332059187d735a1f8b
BLAKE2b-256 checksum
How to use checksums
91accc4c408f814cf096fc36f8b315a0ff7953e2a6c3e2d0eb466421e0b02c0a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for ruff-odoo 0.17.0.35

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.17.0.35 This release

18 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page