-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Heads-up about the new PyPI #1569
Heads-up about the new PyPI #1569
Comments
Hi @brainwane - thanks for posting about this. As a python user I'm eagerly awaiting the removal of the red pre-prod banner.
I've tried switching the base API URL to Would you advise us to switch our production servers over to querying warehouse instead of legacy PyPI now while warehouse is still technically in pre-prod, or would you advise that we should stick with legacy PyPI until April? |
@chris48s Thank you! My take is that, now that you've checked and your test suite passes, you should wait till you get the email that says "switch now" via https://mail.python.org/mm3/mailman3/lists/pypi-announce.python.org/ which will probably be in April. Also is there any chance you'll be at either of the packaging sprints in the next few months? |
Sorted - cheers. I've signed up to that mailing list. I'll leave this issue open for now and close it once we switch over.
I don't currently have plans to, but thanks for the info :) |
Hi. I'm the project manager for the new Python Package Index (Warehouse), which is currently in pre-production at http://pypi.org/ . Your code integrates with the old PyPI API, so I wanted to make sure you knew that, on the Warehouse roadmap, it looks like the full switch will happen sometime in April. 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.Shields 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. And here's the reference for the updated APIs.
Some new PyPI features:
Things that are going away, or already have (sometimes for policy or spam-fighting reasons), include:
And in the works:
You can subscribe to this announcements list to get a heads-up when the big changes are about to happen.
Thank you for integrating with PyPI, and please let us know if you have any questions or problems with the new site!
The text was updated successfully, but these errors were encountered: