Monday as beta day
to be blog post
|Deletions are marked like this.||Additions are marked like this.|
|Line 4:||Line 4:|
|['''This page is a draft''' and ''not to be used/publicized'' until we close out [[https://github.com/pypa/warehouse/milestone/10|the "publicize beta" milestone]]. We plan to do that on Monday, March 26, 2018.]||['''This page is a draft''' of an upcoming PSF blog post and ''not to be used/publicized'' until we close out [[https://github.com/pypa/warehouse/milestone/10|the "publicize beta" milestone]]. We plan to do that on Monday, March 26, 2018.]|
PyPI beta announcement
[This page is a draft of an upcoming PSF blog post and not to be used/publicized until we close out the "publicize beta" milestone. We plan to do that on Monday, March 26, 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.
The legacy PyPI site https://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 http://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.
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 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) 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 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
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)
- 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)
Things that will go away once legacy PyPI shuts down:
Late 2018 or later:
deprecating the XML-RPC API and rearchitecting our APIs
See our issue tracker. Includes:
more timely package name takeovers (PEP 541)
For updates, please sign up for the low-traffic PyPI announcements email list.
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.
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.
- Register/confirm a new user
- Reset password
- Search for projects
- Download release files via browser
- Call JSON, RSS, Simple, and XML-RPC APIs
- 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
Confirm display of project description, release history, download files, project links, maintainers, tags, and classifiers (example)
IRC/Twitter livechat hours
Tuesday, March 27th, 9am-noon PDT, noon-1pm EDT, 18:00-19:00 CEST, 9:30pm-10:30pm India, 16:00-17:00 UTC
Friday, March 30th, 10-11am EDT, 16:00-17:00 CEST, 7:30pm-8:30pm India, 14:00-15:00 UTC
Feel free to drop in! (By participating, you agree to abide by the PyPA Code of Conduct.)
Security issues: email security @ python dot org
GitHub for all other bug reports & feature requests:https://github.com/pypa/warehouse/issues/new
Email: pypa-dev mailing list
(By participating, you agree to abide by the PyPA Code of Conduct.)
Thank you for using PyPI!