mirror of
https://github.com/vinta/awesome-python.git
synced 2026-10-06 17:05:16 +08:00
Vinta ChenandClaude
66ac5fc775
Add a Stability Exceptions section to docs/audit-logs.md documenting the zensical override (admitted pre-1.0 to displace a dying mkdocs upstream). Add a matching evidence bullet to CLAUDE.md and AGENTS.md warning that a download count is not automatically independent demand when one listed entry depends on another, using mkdocs / mkdocs-material as the worked example. Both facts were discovered during this sitting and need to persist so the next audit doesn't rediscover them. Co-Authored-By: Claude <noreply@anthropic.com>
16 lines
1.7 KiB
Markdown
16 lines
1.7 KiB
Markdown
# AGENTS.md
|
|
|
|
An opinionated guide to the best Python frameworks, libraries, and tools.
|
|
|
|
[README.md](README.md) is the single source of content truth; `website/` renders it into the static site: [awesome-python.com](https://awesome-python.com/).
|
|
|
|
## Entry Rules
|
|
|
|
[CONTRIBUTING.md](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.
|
|
- A download count is not automatically independent demand. When one listed entry depends on another, check `requires_dist` on PyPI before citing the depended-on entry's count: mkdocs-material hard-depends on mkdocs, so mkdocs' figure exceeded mkdocs-material's by only about one percent and nearly all of it was mkdocs-material pulling it in.
|
|
- 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](SPONSORSHIP.md).
|