td-python-coding-guidelineslisted

# Google Python Coding Guidelines (Google PyGuide) Aligned with the official document: <https://google.github.io/styleguide/pyguide.html>. Coverage: section 2 language rules (2.1-2.21) and section 3 style rules (3.1-3.19). ## Reference Files | File | Scope | When To Load | | --- | --- | --- | | `references/language-rules.md` | Section 2.1-2.21 language-level rules: lint, imports, exceptions, default values, truthiness, decorators, threading, `__future__`, general type-annotation rules, and related topics. | Before writing or refactoring code. | | `references/style-rules.md` | Section 3.1-3.18 style-level rules: semicolons, line length, whitespace, comments, docstrings, strings, logging, TODOs, import formatting, naming table, main, and function length. | When writing, formatting, or standardizing style. | | `references/exceptions.md` | Deep dive for section 2.4: `assert` boundaries, custom exceptions, the two catch-all exceptions, exception chaining, `Raises:` constraints, and anti-patterns. | When handling exceptions or reviewing error paths. | | `references/type-annotations.md` | Section 2.21 and 3.19.1-3.19.16 type annotation details: NoneType, TypeAlias, TypeVar, generics, `TYPE_CHECKING`, and related topics. | When annotating public APIs, refactoring types, or migrating typing usage. | | `references/review-checklist.md` | A-N review checklist with an output template. | During code review. | ## Workflow 1. **Identify the task type** - Writing or refactoring code: