Warehouse: All New PyPI is now in beta

This was originally posted on blogger here.

![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhDdnT20o2fMIk- kKfMqaKn1UX- YICGDwKXuO51bg67Q1Q4bl3bavFTItZMmCX5E6Cqz1f3eJ4f8-2Ihl8jwV4L77Lbv8N49coyegcrfgWpNQa4kBpPtDIVu7e2PmQnPE-A8A/s1600/logo- large.png)

  1. Context

  2. Migrating

  1. New PyPI Features

  2. Deprecations

  1. Future Plans

  2. Security

  3. Please test!

  1. Workflows

  1. IRC/Twitter livechat hours

  2. Contact us

The all new Python Package Index is now in beta at pypi.org. We predict the full switch will happen in April 2018 (roadmap), so here’s a heads-up about why we’re switching, what’s changed, and what to expect. To get an email when the new site replaces the old one, please sign up for the low- traffic PyPI announcements email list.

Context

The legacy PyPI site at pypi.python.org started in the early 2000s, before modern web frameworks. The legacy codebase has made it hard to maintain and even harder to develop new features, even as past maintainers put in tremendous effort to continuously reduce outages.

The new PyPI at pypi.org (codebase: Warehouse) looks more modern, and is up- to-date under the hood too. A modern web framework (Pyramid), 100% backend test coverage, and a Docker-based development environment make it easier for current and new developers to maintain and run it and add features.

Thanks to Mozilla’s Open Source Support funding, we have designed and added new features, overhauled infrastructure, and worked towards redirecting traffic to the new site and shutting down the old one. 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.

Migrating

You may not need to change anything right away. Thanks to redirects, your sites, services, and tools will probably be able to seamlessly switch to the new site.

Users : On Windows and Linux, no change is necessary as long as your version of OpenSSL supports TLSv1.2. pip install should work as normal. macOS/OS X users running version 10.12 or older need to upgrade to the latest `pip (9.0.3) <https://pypi.org/project/pip/9.0.3/>`_ to connect to PyPI securely:

` ` ` curl <https://bootstrap.pypa.io/get-pip.py> | python`

Package maintainers : If you use setup.py upload to upload releases, we recommend you switch to Twine. New PyPI takes the same username/password as legacy PyPI did. If you have problems, follow the packagers’ migration guide.

API users : follow the API users’ migration guide.

If you’re affected by a deprecation (below), you should adapt and migrate by early April 2018. For help, come to a livechat or contact us. Sign up for `the low-traffic PyPI announcements email list <https://mail.python.org/mm3/mailman3/lists/pypi-announce.python.org/>`_to get a heads-up when we have a more precise date.

New PyPI Features

  • mobile-responsive UI

  • chronological release history for each project (example)

  • easy-to-read project activity journal for project maintainers

  • better search and filtering

  • support for multiple project URLs (e.g., for a homepage and a repo)

  • support for Markdown READMEs for source distributions (soon: wheels too)

  • user-visible Gravatars and email addresses for maintainers

  • no need to “register” a project before initial upload

  • better accessibility (and more work to come)

  • newer backend infrastructure, supporting new features and a more scalable PyPI

Deprecations

Things that already have gone away (sometimes for policy or spam-fighting reasons) include:

Things that will go away once legacy PyPI shuts down:

Late 2018 or later:

Future plans

See our issue tracker. Includes:

For updates, please sign up for the low-traffic PyPI announcements email list.

Security

If you find any potential security vulnerabilities, please follow our published security policy. Please don’t report security issues in Warehouse via GitHub, IRC, or mailing lists. Instead, please directly email the security team.

Please test!

The point of the beta is to find and fix bugs. Please help us. Most of these workflows you can test on pypi.org, using the same login as you use on pypi.python.org (legacy PyPI). For testing destructive actions, like removing an owner, deleting a project, or deleting a release, please use test.pypi.org.

Workflows

Package users:

  • Register/confirm a new user

  • Login/logout

  • Reset password

  • Search for projects

  • pip install a package

  • Download release files via browser

  • Call JSON, RSS, Simple, and XML-RPC APIs

Project maintainers:

  • Add/remove a maintainer

  • Add/remove an owner

  • Transition ownership

  • Remove a project

  • Remove a release

  • View journals for a project

  • View journals for a release

  • Upload a new release (source distribution and wheel; upgrade your versions of twine and setuptools first)

  • Confirm display of project description, release history, download files, project links, maintainers, tags, and classifiers (example)

IRC/Twitter livechat hours

Warehouse developers will be in IRC, in #pypa-dev on Freenode, and on Twitter (#newpypi), available to talk about problems you run into, or about how to hack on Warehouse:

Feel free to drop in! (By participating, you agree to abide by the PyPA Code of Conduct.)

Contact us

(By participating, you agree to abide by the PyPA Code of Conduct.)

Thank you for using PyPI!

![Tobacco Warehouse in Louisville, Kentucky 1906](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj1HseUnTUXRtNqvxugEWezvQIw8QS57_r7phqXUhyx9FBvbnbnJFFpro-1YtFJyCwttL3rsB2vKDzltn1M6fq_LgFwiAjHuOjJq2AmlUCcFeEoyRJ_4QRyxAK6_AVRgr3EzQ/s1600/Tobacco_Warehouse_in_Louisville%252C_Kentucky_1906.jpg)

Previous: Python package maintainers, help test the new PyPI!   Next: Python Developers Survey 2017 Results: Learn about the community