python-excellence

To enforce Python code formatting and typing, you need full type annotations, black and isort formatting, and ruff-clean output. This ensures consistent design, safe resource handling, and eliminates unsafe constructs like mutable defaults and bare excepts.

The best way to review Python code for anti-patterns is to reject mutable defaults, bare excepts, eval, exec, and assert-based validation. Enforcing principal-engineer standards eliminates shadowed built-ins and unsafe type checks for production-safe modules.

To make Python functions and classes idiomatic, use dataclasses, context managers, pathlib, and keyword-only arguments. Production-safe code requires explicit public APIs, careful use of Any, and modern union syntax with built-in generics and Protocols.

Yes, this principal-engineer Python standard applies to source files, notebooks, and project configuration. It enforces typing, formatting, and async patterns across all code generation and review scenarios for consistent, idiomatic output.

You should avoid mutable defaults and bare excepts because they are unsafe anti-patterns. Rejecting them, along with eval, exec, and assert-based validation, ensures safe resource handling and creates robust, production-safe Python code.