DRAFT

PyPI beta announcement

[This page is a draft and not to be used/publicized until we close out the "publicize beta" milestone. That'll probably be by March 25, 2018.]

The new Python Package Index is now in beta at https://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 https://pypi.python.org started in the early 2000s. Users face outages, malicious packages, and spam attacks, and the legacy codebase has made it hard to maintain and even harder to develop new features.

The new PyPI http://pypi.org/ (codebase: Warehouse) looks more modern, and is up-to-date under the hood too; 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, 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: No change necessary. pip install works as normal.

Package maintainers: Use Twine to upload releases, and update the URL you upload to. New PyPI takes the same username/password as legacy PyPI did. 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 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
• far better backend infrastructure, reducing the frequency of outages

Deprecations

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

• uploading via pypi.python.org: uploads must go through the new site's API

• creating a user account on pypi.python.org: new user account registration now only on pypi.org

• uploading to pythonhosted.com documentation hosting (discussion and plans)

• download counts visible in the API: instead, use the Google BigQuery service)

• key management: PyPI no longer has a UI for users to manage GPG or SSH public keys

• uploading new releases via the web UI: instead, we recommend the command-line tool Twine

• updating release descriptions via the web UI: instead, to update release metadata, you need to upload a new release (discussion)

• uploading a package without first verifying an email address

• HTTP access to APIs; now it's HTTPS-only

Things that will go away once legacy PyPI shuts down:

• GPG/PGP signatures for packages (still visible in the Simple Project API per PEP 503, but no longer visible in the web UI)

• OpenID and Google auth login

Late 2018 or later:

• deprecating the XML-RPC API and rearchitecting our APIs

Future plans

See our issue tracker. Includes:

• more timely package name takeovers (PEP 541)

• two-factor authentication

• a user support ticket system

• change your own username

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:

1. [TBD]
2. [TBD]
3. [TBD]
4. [TBD]

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

Contact us

Security issues: email security @ python dot org

GitHub for all other bug reports & feature requests:https://github.com/pypa/warehouse/issues/new

IRC: #pypa-dev on Freenode (someone's usually there 10am-5pm Central Time on weekdays, or during a livechat)

Email: pypa-dev mailing list

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

Thank you for using PyPI!