Python Project Rules

pythonpep8typingbest-practices

Python coding standards: PEP 8, type hints, project structure, virtual environments, and testing conventions.

Целевые файлы

Файл	Формат
.cursorrules	plaintext
CLAUDE.md	markdown

Содержимое

Language: Python 3.11+. Use type hints everywhere (PEP 484, 585). Style: follow PEP 8. Use ruff for linting and formatting (replaces flake8 + black). Imports: stdlib → third-party → local, separated by blank lines. Use isort. Naming: snake_case for functions/variables, PascalCase for classes, UPPER_CASE for constants. Data models: use dataclasses or Pydantic. Avoid plain dicts for structured data. Strings: f-strings for interpolation. Raw strings for regex. Pathlib for paths. Error handling: catch specific exceptions. Use contextlib for resource management. Virtual environments: always use venv/poetry/uv. Pin dependencies in requirements.txt or pyproject.toml. Testing: pytest with fixtures. Parametrize for multiple inputs. Mock external services. Async: use asyncio for I/O-bound. concurrent.futures for CPU-bound. Security: never use eval/exec with user input. Parameterized SQL queries only. Docs: Google-style docstrings. Type stubs for public APIs. Package manager: ${package_manager}.