Python3

A set of rules for writing and organizing modern Python 3 software. It covers project layout, packaging, naming, formatting, imports, linting, tests, and configuration.

In plain words
What is it for?
Use it when creating or reviewing Python projects, especially those using a src directory, a tests directory, pyproject.toml, formatters, linters, and environment-based configuration.
Why use it?
It gives a coding agent consistent conventions, making Python code easier to read, test, maintain, and package.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/thesethrose/devrules/python3
Clone the repo
git clone --depth 1 https://github.com/TheSethRose/DevRules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,335 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01335
Opus 5 $0.00000 $0.00668
Sonnet 5 $0.00000 $0.00267
Haiku 4.5 $0.00000 $0.00134

Measured yesterday against content hash ffb5d4250c40, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Python3 scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/languages/Python3.mdc · 102 lines

How it starts

The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Python 3 Best Practices

Project Structure & Packaging

  • Prefer pyproject.toml for project metadata, build system configuration, and dependencies. Use requirements.txt as a fallback or for specific environment pinning.
  • Use a src-layout: Place main application code inside a src/your_package_name/ directory.
  • Place tests in a tests/ directory parallel to src/.
  • Keep configuration separate (e.g., in environment variables, .env files loaded via appropriate libraries, or dedicated config files/modules).
  • Structure code logically by feature or domain within the src directory.

Code Style & Formatting

  • Adhere strictly to PEP 8.
  • Use an automated code formatter for consistency.
  • Use an import sorting tool for consistent import ordering.
  • Use a linter (identifying style issues, potential bugs, complexity).
  • Configure these tools appropriately (e.g., in pyproject.toml).
  • Naming Conventions (PEP 8):
    • snake_case for functions, methods, variables, and modules.
    • PascalCase (or CapWords) for classes.
    • UPPER_SNAKE_CASE for constants.
    • Leading underscore (_) for internal/protected attributes/methods.
    • Double leading underscore (__) for name mangling (use sparingly).

Language Features & Idioms

  • Use f-strings for string formatting (f"Value is {variable}"). Avoid older formatting methods.
  • Use context managers (with statement) for resources that need cleanup (files, network connections, locks, database connections). Implement __enter__ and __exit__ for custom context managers or use contextlib.
  • Use list/dict/set comprehensions and generator expressions for concise and efficient creation of sequences.
  • Leverage built-in functions and modules (e.g., itertools, collections, functools) where appropriate.
  • Prefer exceptions for error handling over returning error codes or None for exceptional situations.
  • Use pathlib for object-oriented filesystem path manipulation instead of os.path.
  • Use enum.Enum for enumerations.
  • Use dataclasses (or similar libraries) for classes primarily holding data.

Read the full file on GitHub · 102 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 102 lines · 1,335 tokens per session scan A ffb5d4250c40

Subscribe to this mod's changes

Python3 is a cursor rule published in the GitHub repository TheSethRose/DevRules (25 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,335 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.