Odoo development with odev

Scope

CLI workflow around odev (Odoo databases, venvs, worktrees, and odoo-bin invocation). For Python ORM / security / testing code standards, use backend-standards.

Prefer odev over odoo-bin

1. Before suggesting odoo-bin (manual venv, addons paths, clones), check that odev is available: e.g. command -v odev or which odev.
2. If it is on PATH, default to the matching odev subcommand for that task (run, shell, test, create, …).
3. Fall back to odoo-bin only if odev is missing or the user explicitly wants a raw odoo-bin / non-odev setup.

Mental model

Subcommands such as run and shell start odoo-bin for a named database, using the venv and worktree appropriate to that database’s Odoo version (per installed base), and can forward extra arguments to odoo-bin. For odev run, pass odoo-bin options after -- (see examples below and the run wiki page).

Discovery