mirror of
https://github.com/vinta/awesome-python.git
synced 2026-10-02 08:23:10 +08:00
Vinta ChenandClaude
3e43fa13ba
Cross-section re-homes now ride the originating audit's commit instead of needing a separate one, since both sides of the move land in one diff. Also note that Resources sections are out of audit scope and never parsed by the website, so they're not project entries subject to the one-entry-per-commit rule. Co-Authored-By: Claude <noreply@anthropic.com>
1.6 KiB
1.6 KiB
CLAUDE.md
An opinionated guide to the best Python frameworks, libraries, tools, and resources.
README.md is the single source of content truth; website/ renders it into the static site: awesome-python.com.
Entry Rules
CONTRIBUTING.md holds the admission rules, quality requirements, rejection rules, entry format, and ordering. Apply it whenever adding or removing an entry — direct commits included, not only PR reviews.
- Every keep/drop reason must be verified against current online data at decision time — download counts, repo activity and archived status, PyPI metadata, project docs. Judging tiers — obvious choice vs challenger — also requires WebSearch evidence (adoption trajectory, community sentiment), not download counts alone. Training-data recollections are not evidence; label anything unverifiable as a judgment call.
- One entry per commit when adding or deleting entries. Exceptions: a prune sweep is one commit per section, its body listing each removal with its reason; format, wording, or categorization changes may be bundled. Cross-section re-homes ride the originating audit's commit (both sides of the move in one diff).
- Resources sections are not project entries: out of audit scope, and the website never parses them.
- Sponsor placement never influences which projects get listed — see SPONSORSHIP.md.
Gotchas
- On machines with only Python 3.14, prefix uv-based make targets with
UV_PYTHON=3.13— watchdog 6.0.0 ships no 3.14 wheel and the project setsno-build.