GO
Google Python Style Guide
Used in 18 python projects (avg ★6288)
Details
PythonRules
balanced
- Format TODOs as `TODO: @username - specific task` with dates or events; link to issues.
- Place imports at top after module comments/docstrings, before globals/constants.
- Put each import on a separate line; group `typing` and `collections.abc` imports.
- Group imports: future, standard library, third-party, local (most to least generic).
- Use precise TODO descriptions (e.g., 'Fix by November 2009' or 'Remove when clients handle XML') for maintainer clarity.
- Avoid `import os, sys` style; separate lines improve readability and diff clarity.
- Future imports first (e.g., `from __future__ import ...`), ensuring consistent ordering across files.
- No wildcard imports (`from foo import *`) except in unittest cases.