Big news: we have a schedule for April, and we're advising less-intensive API users to switch to hitting pypi.org.

April plans (decided this in yesterday's Warehouse core developers' meeting):

1. Sunday April 8th: TLS 1.0/1.1 removal

2. Monday April 9th: publicize pypi.org launch date (especially to package maintainers and PyPI sponsors)

3. Monday April 16: launch/redirect (API and browser traffic redirected to Warehouse)

4. Monday April 30: shut down legacy PyPI

And today in IRC we decided: If your site/service used to link or upload to pypi.python.org, you should possibly start using pypi.org instead. Now.

Specifically:

If you have an automated tool that hits pypi.python.org less often than once a second, and/or you are fine with small service interruptions during the beta, then you should go ahead and start using pypi.org now, and subscribe to the PyPI announcement list (low-traffic) for further announcements.

If you run a mission-critical automated production setup, or an automated tool that hits pypi.python.org with 1+ requests/second, then you should not explicitly point to pypi.org yet, but you should test and prepare to switch. You should also watch our status page, since we’re occasionally redirecting portions of that traffic in load tests that we announce on the status page. Subscribe to the PyPI announcement list (low-traffic) to find out when you should switch permanently.

Now the more general work update. It's huge because we've been doing so much, our volunteers are prolific, and I truncated last week's report so this is a double issue and I will understand if many of you say "TL;DR".

We have 13 open issues till we can launch and redirect pypi.python.org traffic to Warehouse, and then we have 9 open issues till we can shut down legacy PyPI (overview). We've been whittling away at that pile, and fixing other issues as they come up, while responding to new bug reports (and praise) over the last few weeks (a bit slower because of some (planned) team absences).

Some improvements from the last two weeks from the MOSS-funded team:

our API docs are more accurate and include policies
our "browse" page has default text and suggested searches, and adjusts to page width
prep in case we ever need to briefly turn the site read-only during maintenance
project pages point you to sources for project stats and release notifications
notifications (banners) are dismissable
performance and indexing/caching-related improvements, e.g., purging projects & user pages when someone's role changes, updating the trending projects, and updating the search index more often
activity journal item order is more consistent and deterministic
a project's last serial ID is available via Simple & JSON APIs

Also, Nicole did a bunch of cross-browser testing, Ernest worked on a docs proxy and updated parts of legacy PyPI to point to Warehouse, Dustin fixed issues affecting twine --skip-existing and a classifier error, and I improved developer docs and classifier order. And Warehouse founder and continuing contributor Donald Stufft moved email handling into a service, improved performance, and removed TLS 1.0/1.1 support.

It's deeply important to me to spread the word about the beta, so as many of our friends, neighbors, and colleagues as possible can try Warehouse before the big switch, and so we can know about potential showstoppers as early as possible. So we've held multiple virtual office hours (IRC logs from today's chat), and we've posted to Python-specific spaces like the Python Insider blog and python-announce and debian-python, but we've also done some work to get the word out to programmers who don't particularly pay attention to English-language Python-specific news. We found volunteers to translate and post the announcement a little (Brazilian Portugese, Polish), and reached out to (for instance) Software & Data Carpentry, NumFOCUS, The Changelog, FLOSS Weekly (who'll interview Ernest and Dustin on May 2nd), and Public Lab. I have a giant checklist and I have been crossing many things off. It's very satisfying.

I tried out combining our IRC livechats with a Twitter hashtag, #newpypi, and have gotten approximately zero questions through that so far. Regardless: enjoy some screenshots!

And overlapping with the beta rollout, we've been deprecating TLS 1.0/1.1, which leads to issues on some Macs, which leads to a question from Guido that isn't answered yet.

And other volunteers wrote, by my count, 21 pull requests that we merged over the last 2 weeks. jonparrott, nitinprakash96, venthur, pgadige, saxenanurag, cheungnj, yeraydiazdiaz, AyumuKasuga, jMuzsik, and aalmazan, thank you so much for all your work! I am particularly grateful that our volunteers are helping review each other's work, which helps everyone learn and improve PRs faster.

How you can help:

forward the beta announcement to downstreams
tell people on Macs to upgrade pip, and answer Guido's question about which users are potentially affected
test Warehouse pull requests, and consider making one
talk with Nicole about being a subject or interviewer for user tests
improve the official Python packaging guide
remind well-off companies/foundations you know that further Warehouse work is more likely if they give the PSF donations, sponsorship, or grants

Thanks again to the Mozilla Open Source Support grant that makes this work possible.

Sumana Harihareswara

Warehouse project manager

Changeset Consulting

sh@changeset.nyc