python-anti-patterns

To catch Python anti-patterns before merging, scan your function or module against a code review checklist identifying risky patterns like bare exception swallowing, blocking in async code, and untyped public APIs to prevent production bugs.

Common Python error handling anti-patterns to avoid include bare exception swallowing, ignored partial failures, scattered retry logic, and inadequate error-path testing, all of which severely degrade application reliability and maintainability.

Diagnose blocking calls in Python async code by applying debugging guidance that scans for risky patterns where mixed I/O and business logic block the event loop, explaining each finding with a concrete fix to restore async performance.

Yes, you can use a Python code review checklist for refactoring untyped public APIs by removing exposed internal types, ORM type leakage, and missing type hints to significantly improve your architecture and maintainability.

The best way to find hard-coded secrets and unclosed resources in Python is scanning for specific risky patterns during development, validating configuration handling and resource management to prevent security and infrastructure failures.