Mirrors_Framework/awesome-python
1
0
Fork 0
mirror of https://github.com/vinta/awesome-python.git synced 2026-10-08 00:53:22 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'dual-listing-graphify'

Browse Source
This commit is contained in:
Vinta Chen
2026-10-02 13:08:33 +08:00
parent 172742c3bb 1236c5c5ab
commit 640b9f3423
3 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CONTRIBUTING.md
+1 -1
View File
@@ -27,7 +27,7 @@ Hard maximum: 5 entries per use case. This is a qualitative bar first and a nume
**Displacement**: once a use case is at its cap, the only way in is to name the entry your project replaces and argue that yours does that entry's job better. One in, one out.
**Dual-listing**: a tool may hold entries in multiple use cases, but only when it earns its slot in each independently. List the full entry in each home with identical lines; never a "see X above" note, since the website only renders list items. Description edits update every copy in the same commit. Each slot is audited on its own: dropping one home keeps the other, and dropping the tool entirely removes all copies in one commit. Dual-listing is a maintainer decision; a PR adding a second home for an existing entry is treated as a duplicate.
**Dual-listing**: a tool may hold entries in multiple use cases, but only when it is an obvious choice in each. List the full entry in each home with identical lines; never a "see X above" note, since the website only renders list items. Description edits update every copy in the same commit. Each slot is audited on its own: dropping one home keeps the other, and dropping the tool entirely removes all copies in one commit. Dual-listing is a maintainer decision; a PR adding a second home for an existing entry is treated as a duplicate.
**Standard library**: a standard-library module is listed only where the stdlib is itself the obvious choice for the use case (tomllib yes, unittest no).
docs/audit-logs.md
+1
View File
@@ -14,6 +14,7 @@ Display names follow the canonical PyPI package name. These entries keep a diffe
- django-rest-framework -- `djangorestframework`.
- django-rules -- `rules`.
- fasthtml -- `python-fasthtml`.
- graphify -- `graphifyy`.
- jinja -- `Jinja2`.
- mem0 -- `mem0ai`.
- pangu.py -- `pangu`.
website/data/pypi_name_overrides.json
+1 -1
View File
@@ -14,7 +14,7 @@
"fasthtml": { "package": "python-fasthtml", "reason": null },
"geodjango": { "package": null, "reason": "part of Django (django.contrib.gis), not a package" },
"google-cloud-python": { "package": null, "reason": "monorepo umbrella; ships as many google-cloud-* packages", "badge": "Multiple on PyPI" },
"graphify": { "package": null, "reason": "GitHub-only so far; young project, remap if it publishes" },
"graphify": { "package": "graphifyy", "reason": null },
"httpx-url": { "package": null, "reason": "class in the httpx package, not a package" },
"jev-ultrafast": { "package": null, "reason": "not published on PyPI" },
"jinja": { "package": "jinja2", "reason": "PyPI jinja is Jinja1; current releases publish as jinja2" },