mirror of
https://github.com/vinta/awesome-python.git
synced 2026-10-02 08:23:10 +08:00
docs: require live verification of keep/drop reasons
Qualitative keep/drop reasoning previously relied on training-data recollections that went unverified while only download numbers were checked live, as happened in the Data & Science preview. Key Rules now require every keep/drop reason to be verified against current online data at decision time. Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -28,4 +28,5 @@ An opinionated list of Python frameworks, libraries, tools, and resources. Publi
|
||||
- A shortlist, not a catalog: per use case, up to 3 obvious choices plus up to 2 challengers, hard maximum 5.
|
||||
- One project per PR.
|
||||
- One entry per commit when adding or deleting entries. Exception: a prune sweep is one commit per section, its body listing each removal with its reason. Format, wording, or categorization changes across multiple entries may be bundled in a single commit.
|
||||
- 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. Training-data recollections alone are not evidence; verify before stating, and label anything unverifiable as a judgment call.
|
||||
- README.md is the single source of content truth.
|
||||
|
||||
Reference in New Issue
Block a user