The old intro recommended Kitten TTS and VibeVoice, which the 2026-10-02 audit removed from the README section.
Co-Authored-By: Claude <noreply@anthropic.com>
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>
jev-ultrafast is not published on PyPI but had no null override, so every download sweep queried PyPI for it and recorded NOT_FOUND.
Co-Authored-By: Claude <noreply@anthropic.com>
The download sweep queried PyPI by display name, but PyPI conda is a stale 2017 upload and PyPI pyodide is a 0.0.2 placeholder, so the site showed unrelated packages' download counts for both entries.
Co-Authored-By: Claude <noreply@anthropic.com>
Removed: tkdesigner (317 downloads/month, ClickPy 2026-10-01): its only PyPI release, 1.0.7 (2023-01-22), pins Pillow<9, requests==2.25.1 and urllib3<2, so it has no installable wheels on Python 3.11+, which reverses the August keep. gooey (6,049/month): no release since 1.0.8.1 on 2021-06-12. Dropping gooey empties Wrappers, so the subcategory is dissolved and its URL redirects to /categories/gui-development/. Also: Desktop re-tier, dearpygui up to obvious choice (the only Desktop entry that grew since August) and wxPython down to Second Tier (about half its August downloads).
Co-Authored-By: Claude <noreply@anthropic.com>
Removed: repowise (14,584 downloads/month, pypistats 2026-10-02): no adoption trajectory (about 33K in August to 19.5K on ClickPy), and it left Code Analysis with three challengers against a limit of two. monkeytype (529,705/month): fails the 12-month activity line (default branch last commit 2025-06-14, last release 2023-03-20). Dropping monkeytype empties Type Annotations Generators, so the subcategory is dissolved and its URL redirects to /categories/code-analysis/.
Co-Authored-By: Claude <noreply@anthropic.com>
This lead followed the same appositive frame as the other category intro leads ("X, a/the Python Y library ..."), so it read as one template with the category swapped in; it now has its own sentence frame, keeping the same picks and facts.
Co-Authored-By: Claude <noreply@anthropic.com>
This lead followed the same appositive frame as the other category intro leads ("X, a/the Python Y library ..."), so it read as one template with the category swapped in; it now has its own sentence frame, keeping the same picks and facts.
Co-Authored-By: Claude <noreply@anthropic.com>
This lead followed the same appositive frame as the other category intro leads ("X, a/the Python Y library ..."), so it read as one template with the category swapped in; it now has its own sentence frame, keeping the same picks and facts.
Co-Authored-By: Claude <noreply@anthropic.com>
This lead followed the same appositive frame as the other category intro leads ("X, a/the Python Y library ..."), so it read as one template with the category swapped in; it now has its own sentence frame, keeping the same picks and facts.
Co-Authored-By: Claude <noreply@anthropic.com>
This lead followed the same appositive frame as the other category intro leads ("X, a/the Python Y library ..."), so it read as one template with the category swapped in; it now has its own sentence frame, keeping the same picks and facts.
Co-Authored-By: Claude <noreply@anthropic.com>
This lead followed the same appositive frame as the other category intro leads ("X, a/the Python Y library ..."), so it read as one template with the category swapped in; it now has its own sentence frame, keeping the same picks and facts.
Co-Authored-By: Claude <noreply@anthropic.com>
This lead followed the same appositive frame as the other category intro leads ("X, a/the Python Y library ..."), so it read as one template with the category swapped in; it now has its own sentence frame, keeping the same picks and facts.
Co-Authored-By: Claude <noreply@anthropic.com>
This lead followed the same appositive frame as the other category intro leads ("X, a/the Python Y library ..."), so it read as one template with the category swapped in; it now has its own sentence frame, keeping the same picks and facts.
Co-Authored-By: Claude <noreply@anthropic.com>
This lead followed the same appositive frame as the other category intro leads ("X, a/the Python Y library ..."), so it read as one template with the category swapped in; it now has its own sentence frame, keeping the same picks and facts.
Co-Authored-By: Claude <noreply@anthropic.com>
The rembg paragraph linked the same GitHub URL twice; the model-license link now points at the README's models section, where that claim is stated.
Co-Authored-By: Claude <noreply@anthropic.com>
The intro named Ultralytics' license with its version, AGPL-3.0, against the rule that intros name a license by family only.
Co-Authored-By: Claude <noreply@anthropic.com>
The File Manipulation category page had no intro, showing only the table with a generic meta description.
Co-Authored-By: Claude <noreply@anthropic.com>
The Recommender Systems category page had no intro, showing only the table with a generic meta description.
Co-Authored-By: Claude <noreply@anthropic.com>
The Configuration Files category page had no intro, showing only the table with a generic meta description.
Co-Authored-By: Claude <noreply@anthropic.com>
The Interactive Interpreter category page had no intro, showing only the table with a generic meta description.
Co-Authored-By: Claude <noreply@anthropic.com>
a942b13 dropped this as redundant with the header link, but readers who finish the guide below the table never see that header link and lose the pointer to Package Management entirely.
Co-Authored-By: Claude <noreply@anthropic.com>
Vinta ChenandClaude