Verified history
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean PyPI has never changed. Undated values are kept in the current baseline below instead of being presented as history.
Current monitored baseline
HyperObserve currently monitors 3 scoped observations for PyPI. The baseline covers per-file upload, aggregate project storage, API rate posture. Each value retains its plan, product, endpoint, region, account, or runtime qualifier so a future change can be compared against the correct scope.
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| per-file uploadProjects can request an increase through the documented process when justified. | 100 MB | Default project limit | Python Packaging AuthorityAug 22, 2026 |
| aggregate project storageAll release files for the project contribute to aggregate storage. | 10 GB | Default project limit | Python Packaging AuthorityAug 22, 2026 |
| API rate posturePyPI requires responsible access, caching, identification, and supported APIs. | No current edge-wide numeric rate; XML-RPC may rate-limit | Public APIs | Python Packaging AuthorityAug 22, 2026 |
Tracked constraints and impact
Distribution file, project storage, and responsible API-access limits. A change is recorded only when it alters a constraint developers can act on, such as capacity planning, request shaping, model selection, deployment configuration, storage design, retry behavior, or account budgeting.
PyPI Distribution File Size Limit
PyPI Distribution File Size Limit, verified against PyPI's official documentation with scope, implementation impact, caveats, and a direct check.
PyPI Project Storage Limit
PyPI Project Storage Limit, verified against PyPI's official documentation with scope, implementation impact, caveats, and a direct check.
PyPI API Rate-Limit Policy
PyPI API Rate-Limit Policy, verified against PyPI's official documentation with scope, implementation impact, caveats, and a direct check.
How a change is verified
- Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
- Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
- Preserve the old and new values, official source, effective date when disclosed, detection date, and practical impact. If those elements cannot be supported, no historical event is published.
Official sources monitored
These first-party documents support the current PyPI baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
Per-file and per-project storage limits
API access, caching, and rate-limit posture