Skip to content

The PyPI Blog

Stricter checks for uploaded distributions on PyPI

Over the past few months, PyPI has added some additional checks that can reject uploaded source distributions ("sdists") and built distributions ("bdists" or "wheels").

These checks are part of a larger initiative to make the Python packaging ecosystem more resistant to parser differentials, and will be followed by additional checks that aim to make PyPI's handling of distributions less permissive and more strictly conformant to their respective specifications.

For downstream users (package consumers), there are no breaking implications to these changes. Package maintainers who see failures should ensure that they're using non-EOL versions of Python as well as build backends that produce distributions that properly conform to the packaging standards.

PyPI now limits versions to 128 characters

PyPI now rejects new uploads whose version is longer than 128 characters.

This affects almost no one: across the roughly 9.9 million releases on PyPI, only 2 have a version that long. Releases that are already on PyPI stay exactly as they are, and installing them works the same as before.

Checking email reputation, and allowing Outlook again

PyPI improves on checks for the reputation of an email address when used to register an account or add to an existing account, and rejects addresses identified as disposable.

With the new check in place, outlook.com and hotmail.com addresses can once again be used on PyPI.

Incident Report: File Hosting Errors

Executive summary

For about two weeks in August 2026, some PyPI users hit intermittent 502 and 503 errors downloading files from files.pythonhosted.org, triggering failures during installation from PyPI. Thanks to our users filing reports in the support tracker; one report in particular narrowed the problem to a single cache node.

Two separate problems were uncovered. A canary deployment inside Fastly's network had triggered a misconfiguration at one cache node, causing Fastly's routing layer to return 502 responses for traffic reaching the affected cache node. Separately, I found and fixed several bugs in our own Fastly configuration around origin fallback and range request behavior. Those had been there for a while, and only surfaced while digging into these reports.

Both intermittent problems are now fixed, and downloads are back to full function since August 28.

How AWS Powers PyPI and the PSF

Working on infrastructure at the Python Software Foundation (PSF) as the Director of Engineering is a broad job with many hats. Python turns up everywhere. It's in healthcare systems and government agencies, in research labs and classrooms, in one-person side projects and in infrastructure at companies with six-figure headcounts. Somebody is using it to analyze a genome right now and somebody else is using it to automate a spreadsheet they hate arranging by hand. That range has always been the interesting part of the PSF's work, and it's only broadened in the last couple of years as AI continues to pull people from many disciplines into writing Python.

The HTML representation of the index API is now frozen

PyPI has adopted PEP 833, which "freezes" the HTML representation of the index API, which is also sometimes called the "simple API" or the "simple repository API."

New packages and releases will continue to appear in the HTML representation, meaning this has no breaking implications for downstream index consumers.

However, future standardization and development efforts will focus on the JSON representation, and downstreams that consume only the HTML representation are strongly encouraged to transition to the JSON representation to ensure access to the latest and greatest index features.