PyPI in 2025: A Year in Review
blog.pypi.org
PyPI in 2025: A Year in Review
1–10 of 43 posts
Re: PyPI in 2025: A Year in Review
#2Great work Dustin and team!
Re: PyPI in 2025: A Year in Review
#3One of the big companies making billions on Python software should step up and fund the infrastructure needed to enable PyPI package search via the CLI, like you could with `pip search` in the past.
Re: PyPI in 2025: A Year in Review
#4One of the big companies making billions on Python software should step up and fund the infrastructure needed to enable PyPI package search via the CLI, like you could with `pip search` in the past.
Funding could help, but it still requires PyPI/Warehouse to ship and operate a new public search interface that is safe at internet scale.
Re: PyPI in 2025: A Year in Review
#5One of the big companies making billions on Python software should step up and fund the infrastructure needed to enable PyPI package search via the CLI, like you could with `pip search` in the past.
Serious question: how important is `pip search` to your workflows? I don’t think I ever used it, back when PyPI still had an XMLRPC search endpoint.
(I think the biggest blocker on CLI search isn’t infrastructure, but that there’s no clear agreement on the value of CLI search without a clear scope of what that search would do. Just listing matches over the package names would be less useful than structured metadata search for example, but the latter makes a lot of assumptions about the availability of structured metadata!)
Re: PyPI in 2025: A Year in Review
#6One of the big companies making billions on Python software should step up and fund the infrastructure needed to enable PyPI package search via the CLI, like you could with `pip search` in the past.
Funding could help, but it still requires PyPI/Warehouse to ship and operate a new public search interface that is safe at internet scale.
They operate a public package hosting interface, how is a search one any harder?
Re: PyPI in 2025: A Year in Review
#7Great work!
Side issue: anyone else seeing that none of the links in the article work? They're all 404s.
Re: PyPI in 2025: A Year in Review
#8Earlier quoted context omitted.
Funding could help, but it still requires PyPI/Warehouse to ship and operate a new public search interface that is safe at internet scale.
They operate a public package hosting interface, how is a search one any harder?
PyPI responses are cached at 99% or higher, with less infrastructure to run.
Search is an unbounded context and does not lend itself to caching very well, as every search can contain anything
Re: PyPI in 2025: A Year in Review
#9Great work! Side issue: anyone else seeing that none of the links in the article work? They're all 404s.
Whoops, sorry about that. Should be fixed now. Happy New Year!
Re: PyPI in 2025: A Year in Review
#10Earlier quoted context omitted.
They operate a public package hosting interface, how is a search one any harder?
PyPI responses are cached at 99% or higher, with less infrastructure to run. Search is an unbounded context and does not lend itself to caching very well, as every search can contain anything
Pypi has fewer than one million projects. The searchable content for each package is what? 300 bytes? That's a 200mb index. You don't even need fancy full text search, you could literally split the query by word and do a grep over a text file. No need for elasticsearch or anything fancy.
And anyway, hit rates are going to be pretty good. You're not taking arbitrary queries, the domain is pretty narrow. Half the queries are going to be for requests, pytorch, numpy, httpx, and the other usual suspects.