Project Summaries¶

The way the Python packaging community is organised is something that I’ve explained in multiple places, in multiple contexts. I figure that it’ll be useful to actually write it down in a single place, so that I don’t have to repeat myself. The Python Packaging Authority The Python Packaging Authority (PyPA) is a fairly loose group of projects that happen to be related to Python packaging. While the PyPA has a formal governance model, there’s no “oversight” or “enforcement” on projects that are part of the PyPA – they are only required to adopt the PSF Code of Conduct and to be accepted by the existing members.

Summary of discussions: We requested the Packaging community for feedback on the proposed survey questions The Python Packaging Survey was conducted in Sept-Oct. The results are summarized here. We asked maintainers/contributors on which they would like to discuss the Packaging Strategy. The most popular option was Discourse. The first part of strategy discussion was about unification of Packaging tools Discussion cue: In the Packaging survey, users indicated that they were looking for mor...

This post is a start of a series I've planned about how packaging currently works in Python, what's wrong with it, and how to cope with the problems. But before I get into the meat of it, I want to ta

This PEP proposes a Python Packaging Council with broad authority over packaging standards, tools, and implementations. Like the Python Steering Council, the Packaging Council seeks to exercise this authority as rarely as possible; instead, they use thi...

In this series I discuss various issues with the Python "ecosystem", in particular the tools and standards involved in packaging and distributing Python projects.

Pip has a lot of problems (that I'll be discussing in future posts in this series), but the good news is that you don't have to resort to heavyweight third-party tools to improve your experience with