Python Programming Guidelines

Problem

Python code can run locally but still drift in style, dependencies, language version, and test coverage after review. This skill turns Python coding guidelines into concrete checks instead of linking to PEP 8 alone.

How It Works

It organizes the work around a pre-commit loop: validate syntax with py_compile, run focused pytest tests, and prefer Python 3.10+ features such as match statements, the walrus operator, and type hints. Dependency handling checks for uv first and falls back to pip, with project isolation through a virtual environment. Style rules cover 4-space indentation, snake_case functions and variables, PascalCase classes, UPPER_CASE constants, and import ordering by stdlib, third-party, and local groups. Common patterns include docstrings, pathlib, context managers, and f-strings.

Boundaries

The guidance is best for new projects and shared repositories where Python 3.10+ is supported. It does not replace architecture, performance tuning, or security audits; teams that require strict PEP 8 line length of 79 should treat the 88-character default as a Black-style convention.