python-dev-guidelines

To set up a Python project structure for Python 3.12 with strict typing, standardize your modules using modern packaging like pip or poetry, enforce type hints with mypy, and organize imports consistently to ensure maintainable code.

The best way to enforce Python linting and testing standards is to configure ruff for linting and use pytest-based tests, which standardizes code quality and validates functionality across modern Python projects.

You do not strictly need Pydantic v2 to use async/await patterns or standard data classes, but adopting Pydantic v2 models ensures strict data validation and aligns with modern Python 3.12+ development guidelines.

Google-style docstrings improve Python code readability by standardizing documentation formats across modules and classes, ensuring that function arguments, returns, and descriptions are consistently structured for maintainability.

You can use poetry for packaging while applying strict mypy typing checks, as these guidelines standardize modern packaging workflows alongside strict typing discipline to maintain robust Python project environments.

You should not apply async/await patterns when synchronous execution is sufficient, as standardizing Python development practices requires matching modern language features to appropriate use cases to avoid unnecessary complexity.