Monday, February 26, 2018

Python package maintainers, help test the new PyPI!

Warehouse is a next-generation Python Package Repository which will replace the existing code base that currently powers PyPI. (See the source code on GitHub, and roadmap for details.) We are seeking maintainers of projects on PyPI to test it and send us bug reports, and we're seeking new contributors to Warehouse.

Since Warehouse must be a reimplementation of the existing PyPI, please focus initially on any differences, missing features, or incorrect behavior that is exhibited on that affect your workflows for account management and package maintainership. We'll be soliciting feedback on other concerns soon! Feedback on user experience, accessibility, and overall ease of use are welcome. Go to the pre-production deployment at and try it out!


Last year, the PSF's Packaging Working Group successfully applied for a grant from Mozilla's Open Source Support program. Mozilla awarded USD 170,000 to get PyPI upgraded. The team's been working since early December—see our progress reports and roadmap—and now has the essential features that package maintainers, and most other users, need.

Guidelines for Particpation

By participating, you agree to abide by the PyPA Code of Conduct.
You should sign up for the PyPI Announcement Mailing List for updates.

Things to test

Most of these you can test on, using the same login as you use on (legacy PyPI). For testing destructive actions, like removing an owner, deleting a project, or deleting a release, please use, which has an entirely separate package index.


  • Add/Remove Maintainer
  • Add/Remove Owner
  • Transition Ownership
  • User Registration and Confirmation
  • Login/Logout
  • Password Reset
  • Remove a project
  • Remove a release
  • View Journals for a Project
  • View Journals for a Release
Warehouse has handled new projects and new release uploads since last summer, so those workflows are not the most important to test now. The list of workflows above are the ones we request you to exercise.


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 one or more of our maintainers.

IRC livechat hours

Warehouse developers will be in IRC, in #pypa-dev on Freenode, and available to talk about problems you run into, or about how to hack on Warehouse:
  1. Tuesday Feb 27th: 1700 UTC / noon-1pm EST
  2. Tuesday Feb 27th: 2300 UTC / 6pm-7pm EST
  3. Thursday March 1st: 1700 UTC / noon-1pm EST
  4. Thursday March 1st: 2300 UTC / 6pm-7pm EST
Feel free to drop in!


We're working hard on nearly every aspect of the Warehouse codebase to get it ready for production deployment and we are shipping features nearly every day, so check back and maybe even try using for your maintainer activities full time. Due to the rate of change some errors, downtime, and outright broken features may occur. We have some automated reporting of the scenarios in place, but let us know!

Reminder: Sign up for the PyPI Announcement Mailing List to be kept in the loop as we continue this process.

Dive into the code

We've improved Warehouse's developer experience substantially in the last few months. We have several open "good first contribution" issues and a guide to getting started. One of our maintainers, Ernest W. Durbin III, wants to help you dive in and to give you Warehouse stickers, and has 30-minute 1:1 slots available to mentor you. We'll also be running a sprint at PyCon North America in May!

Contact us

Thank you for testing Warehouse! You're helping us launch sooner and future users of PyPI will appreciate it.

— The PyPI Team

Photo © Mark Hunter

Wednesday, January 31, 2018

The Python Software Foundation is looking for bloggers!

Interview prominent Pythonistas, connect with the community, expand your circle of friends and learn about events in the Python world!

The Python Software Foundation (PSF) is looking to add bloggers for the PSF blog located at As a PSF blogger you will work with the PSF Communication Officers to brainstorm blog content, communicate activities, and provide updates on content progression. Example of content includes PSF community service awardee profiles, details about global Python events and PSF grants, or recent goings-on within the PSF itself. One goal of the 2017 - 2018 PSF Board of Directors is to increase transparency around PSF activities by curating more frequent blog content.

The Python Software Foundation is a 501(c)(3) non-profit corporation that holds the intellectual property rights behind the Python programming language. We also run the North American PyCon conference annually, support other Python conferences/workshops around the world, and fund Python related development with our grants program. To see more info on our grants program, please read:

Job Description

  • Capacity to contribute one to two blog posts per month
  • Passionate about Python and the global Python community
  • Independently report progress and activities to Python Software Foundation Staff and Communication Officers on a monthly basis
  • Actively brainstorm content ideas for blog content individually as well as with Python Software Foundation Staff and Communication Officers

Needed Experience

  • Ability to work independently and on virtual teams
  • Familiarity with Python programming
  • Experience contributing to a technical blog or website in English
  • Professional proficiency in English

Bloggers for the Python Software Foundation receive a fixed fee per post they write.

To apply please email two to three examples of recent articles (e.g. personal blog, contribution to professional publication) written in English as well as a brief description of your writing experience to Please include in the email subject "PSF Blogger Application - (Your Name)". If you have questions, direct them to as well. The Python Software Foundation will be accepting applications until 11:59:59pm Pacific Standard Time Thursday, March 1, 2018.