I'm the project manager for the new Python Package Index (Warehouse), which is currently in pre-production at http://pypi.org/ . On the Warehouse roadmap, it looks like the full switch will happen sometime in April, so here's a heads-up about why we're switching, what's changed, and what to expect.
The legacy PyPI site at https://pypi.python.org started in the early 2000s. In recent years, users faced outages, malicious packages, and spam attacks, and the legacy codebase made it hard to maintain and even harder to develop new features.
The new PyPI has a far more modern look, and is up-to-date under the hood as well; a proper web framework (Pyramid), 100% backend test coverage, and a Docker-based development environment, make it easier for current and new developers to maintain it and add features.
Thanks to Mozilla's Open Source Support funding, developers have added many new features, overhauled infrastructure, and made steady progress towards redirecting traffic to the new site and shutting down the old one. As of the middle of last year, package releases must go through the new PyPI, and as of late February, new user account registration is only available on the new site. The full switch will include redirecting browser and pip install traffic from the old site; then, sometime in late April or early May, the legacy site will be entirely shut down.
Your site/service will probably be able to seamlessly switch to the new site, and thanks to redirects, may not have to change anything immediately. Here's a migration guide.
Some new PyPI features:
mobile-responsive UI
chronological release history for each project (example)
easy-to-read project activity journal for project maintainers
GPG/PGP signatures for packages (still visible in the Simple Project API per PEP 503, but no longer visible in the web UI
key management: PyPI no longer has a UI for users to manage their GPG or SSH public keys
package maintainers being able to upload a new release via the web UI (instead, the recommended command-line tool is Twine)
package maintainers being able to log in and update release descriptions via the web UI (to update release metadata, they need to upload a new release; see distutils-sig discussion)
I'm the project manager for the new Python Package Index (Warehouse), which is currently in pre-production at http://pypi.org/ . On the Warehouse roadmap, it looks like the full switch will happen sometime in April, so here's a heads-up about why we're switching, what's changed, and what to expect.
The legacy PyPI site at https://pypi.python.org started in the early 2000s. In recent years, users faced outages, malicious packages, and spam attacks, and the legacy codebase made it hard to maintain and even harder to develop new features.
The new PyPI has a far more modern look, and is up-to-date under the hood as well; a proper web framework (Pyramid), 100% backend test coverage, and a Docker-based development environment, make it easier for current and new developers to maintain it and add features.
Thanks to Mozilla's Open Source Support funding, developers have added many new features, overhauled infrastructure, and made steady progress towards redirecting traffic to the new site and shutting down the old one. As of the middle of last year, package releases must go through the new PyPI, and as of late February, new user account registration is only available on the new site. The full switch will include redirecting browser and
pip installtraffic from the old site; then, sometime in late April or early May, the legacy site will be entirely shut down.Your site/service will probably be able to seamlessly switch to the new site, and thanks to redirects, may not have to change anything immediately. Here's a migration guide.
Some new PyPI features:
Things that are going away, or already have (sometimes for policy or spam-fighting reasons), include:
And in the works:
For future updates, please sign up for the low-traffic PyPI announcements email list.
Thank you for integrating with PyPI, and please let us know if you have any questions or problems with the new site!