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.36
    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.
  • The domains of an XML file (the domain, filter_domain and attrs attributes, <attribute name="domain">, and the domain and domain_force fields of a record) are checked by the rules that read domains (scalar-in-domain, ODW9505), each as an expression; a domain Python cannot parse is skipped without a diagnostic.
  • 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.36

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.36+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.36",
  "commit_info": {
    "short_commit_hash": "b45cfcb38",
    "commit_hash": "b45cfcb38d111d9f446b195125290a19e4cf8a4e",
    "commit_date": "2026-08-15",
    "last_tag": "0.17.0.36",
    "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.36

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.36
File Size Uploaded Provenance Actions
ruff_odoo-0.17.0.36.tar.gz 5.5 MB Without provenance Details for ruff_odoo-0.17.0.36.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for ruff-odoo 0.17.0.36
File Actions
ruff_odoo-0.17.0.36-py3-none-win_arm64.whl Python 3 none Windows ARM64 Details for ruff_odoo-0.17.0.36-py3-none-win_arm64.whl
ruff_odoo-0.17.0.36-py3-none-win_amd64.whl Python 3 none Windows x86-64 Details for ruff_odoo-0.17.0.36-py3-none-win_amd64.whl
ruff_odoo-0.17.0.36-py3-none-win32.whl Python 3 none Windows x86-32 Details for ruff_odoo-0.17.0.36-py3-none-win32.whl
ruff_odoo-0.17.0.36-py3-none-musllinux_1_2_x86_64.whl Python 3 none Linux musl 1.2+ x86-64 Details for ruff_odoo-0.17.0.36-py3-none-musllinux_1_2_x86_64.whl
ruff_odoo-0.17.0.36-py3-none-musllinux_1_2_i686.whl Python 3 none Linux musl 1.2+ x86-32 Details for ruff_odoo-0.17.0.36-py3-none-musllinux_1_2_i686.whl
ruff_odoo-0.17.0.36-py3-none-musllinux_1_2_armv7l.whl Python 3 none Linux musl 1.2+ ARMv7l Details for ruff_odoo-0.17.0.36-py3-none-musllinux_1_2_armv7l.whl
ruff_odoo-0.17.0.36-py3-none-musllinux_1_2_aarch64.whl Python 3 none Linux musl 1.2+ ARM64 Details for ruff_odoo-0.17.0.36-py3-none-musllinux_1_2_aarch64.whl
ruff_odoo-0.17.0.36-py3-none-manylinux_2_31_riscv64.whl Python 3 none Linux glibc 2.31+ RISC-V 64 Details for ruff_odoo-0.17.0.36-py3-none-manylinux_2_31_riscv64.whl
ruff_odoo-0.17.0.36-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.36-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
ruff_odoo-0.17.0.36-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.36-py3-none-manylinux_2_17_s390x.manylinux2014_s390x.whl
ruff_odoo-0.17.0.36-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.36-py3-none-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl
ruff_odoo-0.17.0.36-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.36-py3-none-manylinux_2_17_i686.manylinux2014_i686.whl
ruff_odoo-0.17.0.36-py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.whl Python 3 none Linux glibc 2.17+ ARMv7l Details for ruff_odoo-0.17.0.36-py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.whl
ruff_odoo-0.17.0.36-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl Python 3 none Linux glibc 2.17+ ARM64 Details for ruff_odoo-0.17.0.36-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
ruff_odoo-0.17.0.36-py3-none-macosx_11_0_arm64.whl Python 3 none macOS 11.0+ ARM64 Details for ruff_odoo-0.17.0.36-py3-none-macosx_11_0_arm64.whl
ruff_odoo-0.17.0.36-py3-none-macosx_10_12_x86_64.whl Python 3 none macOS 10.12+ x86-64 Details for ruff_odoo-0.17.0.36-py3-none-macosx_10_12_x86_64.whl
ruff_odoo-0.17.0.36-py3-none-linux_armv6l.whl Python 3 none linux armv6l Details for ruff_odoo-0.17.0.36-py3-none-linux_armv6l.whl

Total release size: 188.6 MB

Release files / ruff_odoo-0.17.0.36.tar.gz

Download URL ruff_odoo-0.17.0.36.tar.gz
Size 5.5 MB
Tags Source
SHA-256 checksum
How to use checksums
062a7ccd8dbb1a48fb0e772fd01e45b7535761a33ab1c0baf9d4595a4ea077ee
BLAKE2b-256 checksum
How to use checksums
e4e22ead1d5185f5a5b349d9988270eec7ae4c4ae2ffe23975434c0d2e70ff2e
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.36-py3-none-win_arm64.whl

Download URL ruff_odoo-0.17.0.36-py3-none-win_arm64.whl
Size 10.8 MB
Tags Python 3 Windows ARM64
SHA-256 checksum
How to use checksums
6b56b171927e733bb632ac0f5195f32e4633e8fd227ac2aacd7502a14ed19470
BLAKE2b-256 checksum
How to use checksums
30a8336d82513bdf288b3709b71dca76fad3119b05240f7db190d562044af45d
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.36-py3-none-win_amd64.whl

Download URL ruff_odoo-0.17.0.36-py3-none-win_amd64.whl
Size 10.9 MB
Tags Python 3 Windows x86-64
SHA-256 checksum
How to use checksums
8baa37460427ef4a1ea17f253bb112d51d76c5658ef5271c41a244154201184f
BLAKE2b-256 checksum
How to use checksums
11072217a5078b0ab4d05d332e1d85ff573eb074c7a49eac432f918f90372e3f
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.36-py3-none-win32.whl

Download URL ruff_odoo-0.17.0.36-py3-none-win32.whl
Size 10.6 MB
Tags Python 3 Windows x86-32
SHA-256 checksum
How to use checksums
7b65ffb760115d32c394415905df8bb9183f987803bb98b44d8be09b5da7b46b
BLAKE2b-256 checksum
How to use checksums
2212a807a84d3c01f186069eb61ec52f8f1df556bf0d80f5f451872382726003
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.36-py3-none-musllinux_1_2_x86_64.whl

Download URL ruff_odoo-0.17.0.36-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
d95090ec6398d839b9e09dcc61b9f4a1aae00267f33cc64c11c1ad026d9b8406
BLAKE2b-256 checksum
How to use checksums
4b6427a69329c61baa9e30102c09b8fbb3cc617f5353f77b03b86873b0768b90
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.36-py3-none-musllinux_1_2_i686.whl

Download URL ruff_odoo-0.17.0.36-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
738dbdc71719e2f817a8aa1bbb4ce4301958275093ccb2ae5c040c95dbf4ca18
BLAKE2b-256 checksum
How to use checksums
b114aa0561b0ebfd6b1624b17d508f31ca2ad25216a6e4c3abd0027507c582d7
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.36-py3-none-musllinux_1_2_armv7l.whl

Download URL ruff_odoo-0.17.0.36-py3-none-musllinux_1_2_armv7l.whl
Size 10.4 MB
Tags Linux musl 1.2+ ARMv7l Python 3
SHA-256 checksum
How to use checksums
71000f77d0501befe396cf82912e329e7d00eb860dbf14225e002d063078cbb1
BLAKE2b-256 checksum
How to use checksums
a4178ac5a45ae11d04d3cf42adc60579344ac5df0a1ac827127f34d5064a7584
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.36-py3-none-musllinux_1_2_aarch64.whl

Download URL ruff_odoo-0.17.0.36-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
d5f1a91091ab9fc2a879ca67bcd77f40922454e6a8a67dad315535f04fffe2a6
BLAKE2b-256 checksum
How to use checksums
cc84529f16432f0ed303d0615f6d1f1510fe3a930b0c71386449c56410c2eb19
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.36-py3-none-manylinux_2_31_riscv64.whl

Download URL ruff_odoo-0.17.0.36-py3-none-manylinux_2_31_riscv64.whl
Size 11.0 MB
Tags Linux glibc 2.31+ RISC-V 64 Python 3
SHA-256 checksum
How to use checksums
ad96e248e5623818b89cf26a6cb0dfc498afbff10b1fa6084bec5c582ae6f6a6
BLAKE2b-256 checksum
How to use checksums
6aca574489b5fc188ceeaa6c9055715393ba48e31524b40861467e52521bf87a
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.36-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL ruff_odoo-0.17.0.36-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 10.8 MB
Tags Linux glibc 2.17+ x86-64 Python 3
SHA-256 checksum
How to use checksums
109da25e101d1d2936eea4502d114ea60198e855e0d230c8ccbc7a685bb4c8f6
BLAKE2b-256 checksum
How to use checksums
8cf6b76e7000af6be558dd5518668299c526d6835065474809493639ddc7f482
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.36-py3-none-manylinux_2_17_s390x.manylinux2014_s390x.whl

Download URL ruff_odoo-0.17.0.36-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
9f4db9ed53116b8ff00664e48b8190a4793c32c32b97e1109136eee9f2d81b14
BLAKE2b-256 checksum
How to use checksums
1afb3be111f2b167758263f330d704afc6b7c217a10fe70a317959ded8074d6c
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.36-py3-none-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl

Download URL ruff_odoo-0.17.0.36-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
f6288d90209e77b084e24c0096d2e75119333c5547acb9e453a66a6b36faeb05
BLAKE2b-256 checksum
How to use checksums
b78a8770317a7a11655abecb26d6034889bd705df4b72402fb4a29cfc28508d2
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.36-py3-none-manylinux_2_17_i686.manylinux2014_i686.whl

Download URL ruff_odoo-0.17.0.36-py3-none-manylinux_2_17_i686.manylinux2014_i686.whl
Size 11.0 MB
Tags Linux glibc 2.17+ x86-32 Python 3
SHA-256 checksum
How to use checksums
bf74d1b56d25183f354e018bff14005ab390fd76202b1b2b0aab41a42afb1158
BLAKE2b-256 checksum
How to use checksums
8bb7525b1d4ff856695ba3938f625cf374c511672b2e2761ec9daeebde2e1044
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.36-py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.whl

Download URL ruff_odoo-0.17.0.36-py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.whl
Size 10.4 MB
Tags Linux glibc 2.17+ ARMv7l Python 3
SHA-256 checksum
How to use checksums
bba4381751e688ee512dbaaa4427712ea0e1878a3997bc144a19020137b991ab
BLAKE2b-256 checksum
How to use checksums
e8be675dd6d6fec34559229db12f6881356552a427ea6537889bd702c061be48
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.36-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL ruff_odoo-0.17.0.36-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
abcb4061c603b27ecb28d12412b4d2b0104ced41a299a749d0e9260088c9b3ad
BLAKE2b-256 checksum
How to use checksums
46e30e686e6e4aa5f8b6fed5612b7560dbcdc90706f0536ca9b10e829cb4e97e
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.36-py3-none-macosx_11_0_arm64.whl

Download URL ruff_odoo-0.17.0.36-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
0083127fa3b9da5846ef6ec64fb0c4b795a8cdff1ed6fcc6ae03e856f93ab846
BLAKE2b-256 checksum
How to use checksums
c70e9069d95e0e9633623720284467b3867a4552e3c0e29daed478016f6dc42f
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.36-py3-none-macosx_10_12_x86_64.whl

Download URL ruff_odoo-0.17.0.36-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
41e14c295fa57a8adea47175a10b8002aec537c7aab480f58dd4748d0a041fb9
BLAKE2b-256 checksum
How to use checksums
f0c006e95bc0d31ae6318e835455519dae65a59733269b48ad20b80224a83023
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.36-py3-none-linux_armv6l.whl

Download URL ruff_odoo-0.17.0.36-py3-none-linux_armv6l.whl
Size 10.6 MB
Tags Python 3 linux armv6l
SHA-256 checksum
How to use checksums
f724801fa03d70e190e0a45456f5689d49fa651803bd9cc2a3ce73659eedb63c
BLAKE2b-256 checksum
How to use checksums
e114fa947f9de7db56f1a545d1274c3f511d47196ce92cc3affd5287298f9b5b
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.36

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.36 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