mirror of
https://github.com/vinta/awesome-python.git
synced 2026-10-02 08:23:10 +08:00
docs: amend Entry Ordering so standard-library modules sort first in tier
Maintainer rule change: built-ins lead their tier instead of sorting last with the other no-signal entries — a stdlib module that earns a slot is the default answer, so it reads first. Several stdlib modules in one tier stay alphabetical. Non-stdlib no-signal entries (agent skill packs, projects distributed outside PyPI) still sort last in tier. README reorder of already-audited sections follows in a style commit; unaudited sections pick the rule up at their own audit. Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
+1
-1
@@ -44,7 +44,7 @@ The only admission path into a full Use Case: the PR names the entry it replaces
|
||||
_Avoid_: One-in-one-out (informal alias)
|
||||
|
||||
**Challenger**:
|
||||
An entry (at most two per Use Case) that is not yet the Obvious Choice but is a credible successor to one. Marked by ordering, not description: within a Use Case, Obvious Choices are listed first, then Challengers, each tier by PyPI downloads/month descending (no-signal entries last in tier, alphabetically). Admission requires adoption-trajectory evidence, not popularity alone.
|
||||
An entry (at most two per Use Case) that is not yet the Obvious Choice but is a credible successor to one. Marked by ordering, not description: within a Use Case, Obvious Choices are listed first, then Challengers, each tier by PyPI downloads/month descending (standard-library modules first in tier, other no-signal entries last in tier, alphabetically). Admission requires adoption-trajectory evidence, not popularity alone.
|
||||
_Avoid_: Rising Star (old lane name), Hidden Gem (old lane name — concept removed entirely)
|
||||
|
||||
**Second Tier**:
|
||||
|
||||
+1
-1
@@ -73,7 +73,7 @@ Use the **PyPI package name** as the display name so developers can copy it dire
|
||||
|
||||
### Entry Ordering
|
||||
|
||||
Within a use case, the obvious choices are listed first, ordered by PyPI downloads per month from high to low; challengers follow, in the same order. Entries without a download signal (standard-library modules, agent skill packs) sort last within their tier, alphabetically. There is no marker in the entry text — position is the marker, so the last entries of a use case may be its challengers.
|
||||
Within a use case, the obvious choices are listed first, ordered by PyPI downloads per month from high to low; challengers follow, in the same order. Standard-library modules sort first within their tier — built-ins lead — alphabetically when there are several. Other entries without a download signal (agent skill packs, projects distributed outside PyPI) sort last within their tier, alphabetically. There is no marker in the entry text — position is the marker, so the last entries of a use case may be its challengers.
|
||||
|
||||
## Changing the Structure
|
||||
|
||||
|
||||
Reference in New Issue
Block a user