python-code-review

These patterns are intentional and correct - do not report as issues: Only flag these issues when the specific conditions apply: Load and follow review-verification-protocol before reporting any issue. - Type annotation vs type assertion - Annotations declare types but are not runtime assertions; don't confuse with missing validation - Using Any when interacting with untyped libraries - Required when external libraries lack type stubs - Empty __init__.py files - Valid for package structure, no code required - noqa comments - Valid when linter rule doesn't apply to specific case - Using cast() after runtime type check - Correct pattern to inform type checker of narrowed type - Reviewing code formatting/style → pep8-style.md - Reviewing function signatures → type-safety.md - Reviewing async def functions → async-patterns.md - Reviewing try/except blocks → error-handling.md - General Python review → common-mistakes.md - Does the code follow PEP8 formatting (indentation, line length, whitespace)? - Are imports properly grouped (stdlib → third-party → local)? - Do names follow conventions (snake_case, CamelCase, UPPER_CASE)? - Are all function signatures fully typed? - Are async functions truly non-blocking? - Do exceptions include meaningful context? - Are there any mutable default arguments?