From 0b75c7806dcee6356e78899ffee184de75281f5f Mon Sep 17 00:00:00 2001 From: Vinta Chen Date: Fri, 2 Oct 2026 12:36:53 +0800 Subject: [PATCH] docs: judge stability by the project, not its PyPI classifier CONTRIBUTING's Stable requirement read as "not alpha/beta", so about 40 production-used entries (fastapi, uvicorn, keras, statsmodels, numba, and others) failed it on their PyPI Development Status classifier alone, and each needed an audit-log exception. Co-Authored-By: Claude --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index d66b00d9..937d8ee9 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -8,7 +8,7 @@ All submissions must satisfy **ALL** of these: 1. **Serves Python Developers**: Python developers use it in their Python work. Implementation language and packaging are irrelevant — uv and ty are written in Rust, and agent skill packs are markdown, yet all belong; a pure-Python project nobody uses in Python work does not. 2. **Active**: Commits within the last 12 months -3. **Stable**: Production-ready, not alpha/beta/experimental +3. **Stable**: Production-ready, not alpha/beta/experimental. A PyPI "Development Status" classifier alone does not decide this; judge by releases, documentation, and production use. 4. **Documented**: Clear README with examples and use cases 5. **Established**: Repository at least 1 month old