ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #poetry
Stop shipping dev tools to production. Learn how to use Poetry dependency groups and locked builds to separate runtime intent and ensure reproducible CI environments.
Poetry's dependency groups let you keep one lock file while installing only the packages a given environment needs. Learn how --only, --with, and --without work across Poetry 1.x and 2.x.
Poetry refuses to install when pyproject.toml and poetry.lock are out of sync. Use this diagnostic guide to restore consistency without silently upgrading dependencies.
Poetry's default install is additive, so stale packages linger in your virtualenv. Here's how groups, --with, and --sync change that — and the trade-offs.
Choose Poetry dependency groups for internal tooling and extras for consumer-facing optional features. Compare the trade-offs, see a concrete pyproject.toml layout, and validate the result.
Learn how Poetry’s lock file records exact versions and hashes to give reproducible installs, what trade‑offs to watch for, and a step‑by‑step example you can run today.
Poetry's lockfile pins exact package versions and hashes for reproducible installs. Learn when to use poetry lock --no-update and how to verify your dependency tree.
Decide between Poetry dependency groups and optional extras for dev tooling: a comparison, a concrete pyproject setup, and commands to verify production installs stay clean.
Learn how Poetry’s lockfile and solver keep Python environments deterministic, preventing dependency drift. Follow a concrete example, see trade‑offs, and get actionable steps to lock and install reliably.
python