packaging-conventions

Standardize Python packaging by consolidating project metadata, dependencies, and build settings into a canonical pyproject.toml file. This eliminates legacy configurations and enforces consistent build tooling across libraries and applications for reproducible distributions.

The src/ layout convention separates executable package code from project root files to prevent accidental imports during testing. Adopt this layout alongside pyproject.toml to ensure maintainable project structures and reproducible builds across single and multi-package repositories.

Manage multi-package repository dependencies by configuring uv workspaces within pyproject.toml. This approach unifies packaging workflows, coordinates dependency groups across packages, and streamlines maintenance for complex Python monorepos.

Select a build backend and define optional dependency groups directly within pyproject.toml to control how packages are built and distributed. This configuration streamlines publishing workflows and manages environment-specific dependencies for reproducible builds.

Migrate legacy Python configurations by moving project metadata, build settings, and dependencies into pyproject.toml. Adopting this modern packaging standard alongside a src/ layout replaces fragmented configs with unified, reproducible packaging workflows.

Avoid pyproject.toml-centric packaging conventions when working with legacy Python environments that lack modern build tooling support, or when existing setup configurations cannot be safely migrated without breaking complex dependency chains.