Documentation·
pypi/warehouse
Document PyPI project archival behavior and owner workflow
Adds a canonical project archival guide explaining how owners archive projects and what that status means. It distinguishes archival from deletion and documents upload restrictions, existing release availability, and unarchiving.
The problem
The archival documentation previously directed readers to a blog announcement without providing an in-page procedure. It did not explain locally how archival affects installations and uploads or what owners should consider before proceeding.
The approach
Expanded the page with archival semantics and preparation guidance, including considering a final release and updating the project description. Added steps for accessing the Project archival section in project settings and reviewing the upload warning. Documented the archived notice and the owner's ability to unarchive, while retaining the announcement link for background.
What changed
The documentation now provides an owner-facing archival procedure and explicitly states that existing releases remain installable while new file uploads are blocked. It also explains that archived status signals no expected future releases, maintenance, or security fixes.
- pypi
- project-archival
- project-management
- markdown