Anthropic's Python SDK for building AI agents on Claude Code's harness.
~32.6M downloads/month (pepy, 2026-08-15; approximate, includes
mirrors — pypistats was rate-limited). Lands beside openai-agents in
the Vendor Agent SDKs use case minted in the AI and Agents sweep.
Co-Authored-By: Claude <noreply@anthropic.com>
Per ADR-0001, restructure first: split Pre-trained Models and Inference
into Pre-trained Models, LLM Inference and Serving, and LLM Gateways;
mint Vendor Agent SDKs, Personal Assistants, Prompt Optimization, Image
and Video Generation, and Fine-tuning subcategories. Re-home
openai-agents (Vendor Agent SDKs), hermes-agent (Personal Assistants,
description reworded to personal assistant), dspy (Prompt Optimization),
diffusers (Image and Video Generation), unsloth (Fine-tuning), and
graphify (Data Visualization > Specialized). Then cap.
Removed (downloads are PyPI last-month via pypistats, 2026-08-14/15):
- nuwa-skill: persona prompts, not engineering
- crewai (19.4M/month): buzz peaked; no longer named unprompted
- autogen (1.1M/month): fork war with ag2 split its community
- ag2 (441K/month): other half of the same fork war
- smolagents (651K/month): Hugging Face ecosystem niche
- TradingAgents (11.9K/month): vertical trading app, not general
orchestration
- bub (5.6K/month): no adoption
- bindu (210/month): no adoption
- livetalking: no PyPI presence, no adoption evidence
- bernstein: no PyPI presence, no adoption evidence
- promptise: no PyPI presence, no adoption evidence
- OpenChronicle: no PyPI presence, no adoption evidence
- outlines (2.5M/month): same job as instructor, which holds the slot
- entroly (3.1K/month): no adoption
- lumen (1.8K/month): no adoption
- liter-llm (3.5K/month): xberg-io coordinated self-promotion plant
- SenseVoice: whisper wins the use case
- voxcpm (101K/month): no track record
Co-Authored-By: Claude <noreply@anthropic.com>
Land the shortlist-reform rules approved by the maintainer (rules
first; entry sweeps are not authorized yet).
- CONTRIBUTING.md: replace the Industry Standard / Rising Star / Hidden
Gem lanes with a single admission rule per use case (up to 3 obvious
choices + up to 2 challengers, hard max 5), add Displacement, the
stdlib rule, and editorial-judgment-as-final evidence guidance; scope
test becomes Serves Python Developers; document entry ordering
(obvious choices then challengers, each alphabetical).
- README.md: add the shortlist promise paragraph pointing rejected
contributors to linked awesome-* catalogs and to CONTRIBUTING.md.
- CLAUDE.md: sync Key Rules with the new ordering and shortlist cap,
and add the prune-sweep one-commit-per-section exception.
- docs/adr/0001-shortlist-not-catalog.md: flip status from proposed to
accepted.
Co-Authored-By: Claude <noreply@anthropic.com>
A 2026-08-15 grilling round replaced the Challenger marking
convention: within a Use Case, Obvious Choices are listed first
(alphabetically), then Challengers (alphabetically), with no marker
in the entry text. Update the Challenger definition in CONTEXT.md.
Co-Authored-By: Claude <noreply@anthropic.com>
CONTEXT.md review found several definitions had drifted from the
settled shortlist-reform decisions:
- Entry: pypi-name placeholder contradicted the serves-Python-developers
scope test, which explicitly treats implementation language and
packaging as irrelevant; now named by PyPI package name when one
exists, else repository name
- Subcategory: example referenced a name that no longer matches the
current README structure (Mock, not Mocking)
- Thematic Group: referenced elsewhere in the doc but never defined;
added
- Use Case, Obvious Choice, Split: updated to match the settled
cap/evidence/restructure decisions (maintainer-only structure
changes, PyPI-download judgment with known failure modes noted,
Split considered before trimming)
Co-Authored-By: Claude <noreply@anthropic.com>
Per maintainer choice, the new scope test replaces the old primarily-written-in-Python (>50%) requirement: implementation language and packaging no longer matter as long as Python developers use the thing in their Python work (e.g. uv and ty are Rust; agent skill packs are markdown), while pure-Python projects nobody uses in Python work still don't qualify. Folded into the existing ADR rather than filed as a separate one.
Co-Authored-By: Claude <noreply@anthropic.com>
ADR review found three stale claims: an unreviewed Testing dry-run cited as
evidence for the projected list size, the Challenger path missing from the
lane-rejection rationale, and no mention of judgment overriding known
failure modes of the download-signal (CI/dependency-inflated counts, model
weights vs. pip installs, large-but-specific audiences misread as niche).
Co-Authored-By: Claude <noreply@anthropic.com>
Cap changed to 3 obvious choices + up to 2 challengers (hard max 5)
during review, but the ADR still described the old cap of 3 with at
most one challenger.
Co-Authored-By: Claude <noreply@anthropic.com>
Records the outcome of a grilling session with the maintainer that
settled the redesign of awesome-python from a catalog into a curated
shortlist of Obvious Choices per Use Case. Execution is held pending
maintainer go-ahead, so these files let a fresh agent resume without
re-litigating settled decisions:
- CONTEXT.md: glossary of the editorial vocabulary (Use Case, Obvious
Choice, Challenger, Displacement, Split, etc).
- docs/adr/0001-shortlist-not-catalog.md: the ADR recording the
decision, considered options, and consequences (status: proposed).
- .gitignore: docs/ was wholesale-ignored; carve out docs/adr/ so the
ADR can be tracked.
Co-Authored-By: Claude <noreply@anthropic.com>
Python 2 reached end-of-life in January 2020. The 'Python 2/3
compatible' qualifier is no longer relevant and misleading. Updated
to match the official repository description.
The previous description 'JavaScript Object Signing and Encryption
draft implementation' was inaccurate. Authlib is a comprehensive
Python library for building OAuth 1.0, OAuth 2.0, and OpenID Connect
clients and servers.