modern-python

Guide for modern Python tooling and best practices, based on trailofbits/cookiecutter-python . Key principles: See security-setup.md for configuration and usage. For simple multi-file projects not intended for distribution: If starting from scratch, ask the user if they prefer to use the Trail of Bits cookiecutter template to bootstrap a complete project with already preconfigured tooling. This creates: See pyproject.md for complete configuration reference. Key sections: When a user requests migration from legacy tooling: First, determine the nature of the code: For standalone scripts : Convert to PEP 723 inline metadata (see pep723-scripts.md ) For projects : Then: Use uv run --with for one-off commands that need packages not in your project: When to use --with vs uv add : See uv-commands.md for complete reference. Install with: uv sync --group dev --group test - Creating a new Python project or package - Setting up pyproject.toml configuration - Configuring development tools (linting, formatting, testing) - Writing Python scripts with external dependencies - Migrating from legacy tools (when user requests it) - User wants to keep legacy tooling : Respect existing workflows if explicitly requested - Python < 3.11 required : These tools target modern Python - Non-Python projects : Mixed codebases where Python isn't primary - Always use uv add and uv remove to manage...