fix: map graphify to its graphifyy PyPI package

graphify's PyPI override was null (GitHub-only), so the site showed no download count although the project now publishes on PyPI as graphifyy.

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Vinta Chen
2026-10-02 13:08:32 +08:00
co-authored by Claude
parent 545369b667
commit 1236c5c5ab
2 changed files with 2 additions and 1 deletions
+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`.
+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" },