Python project conventions

Standardize Python project structure by enforcing a consistent source layout under src/ or a top-level package, tests under tests/, and dependency files like pyproject.toml or requirements*.txt. This reduces onboarding friction and configuration drift across multi-repo environments by providing repeatable Make targets for install, lint, format, test, and coverage.

A Python project should include standard Make targets for install, install-dev, lint, format, test, coverage, and check. These targets drive consistent development workflows and CI pipelines, ensuring code quality and test coverage are validated uniformly across new and existing repositories.

Yes, this Python project convention validates the presence of pyproject.toml or requirements*.txt files. It explicitly supports expected source layouts under src/ or a top-level package, and requires tests to be located under tests/, accommodating standard Python repository structures.

The best way to onboard new Python projects is to apply standardized Make targets for install, lint, format, test, and coverage. This enforces consistent project conventions from the start, specifying requirements like pyproject.toml and expected source layouts to prevent configuration drift and reduce setup time.

You need a Makefile for your Python development workflow to define repeatable targets for install, lint, format, test, and coverage. This solves the problem of inconsistent development workflows across projects, ensuring that CI pipelines and local maintenance tasks execute consistently without manual setup errors.

Yes, you can use this approach to enforce Python project conventions in existing repositories. It validates the presence of pyproject.toml or requirements*.txt, checks for expected source layouts under src/ or top-level packages, and ensures tests reside under tests/, applying consistent Make targets to ongoing maintenance workflows.