Poetry production installs: per-command `--no-dev` flag or project-level group restriction?
I'm packaging a Python application for production deployment and want to guarantee that development and test dependencies never end up in the production environment. Poetry documents two ways to achieve this: passing --no-dev (or --only main ) to poetry install on each invocation, or restricting installation to the main dependency group at the project config
