Why is Python Packaging
329 | Sat 03 Aug 5:30 p.m.–6:15 p.m.
Presented by
-
Moshe Zadka
https://cobordism.com
Moshe has been involved in the Linux community since 1998, helping in Linux "installation parties". They have been programming Python since 1999, and has contributed to the core Python interpreter. Moshe has been a DevOps/SRE since before those terms existed, caring deeply about software reliability, build reproducibility and other such things. They have worked in companies as small as three people and as big as tens of thousands -- usually some place around where software meets infrastructure.
Moshe Zadka
https://cobordism.com
Moshe has been involved in the Linux community since 1998, helping in Linux "installation parties". They have been programming Python since 1999, and has contributed to the core Python interpreter. Moshe has been a DevOps/SRE since before those terms existed, caring deeply about software reliability, build reproducibility and other such things. They have worked in companies as small as three people and as big as tens of thousands -- usually some place around where software meets infrastructure.
Abstract
"Python packaging is a problem" is a meme. What is Python packaging? What is being packaged, where is it sent from, and where is its destination? Why, oh why, can't I just produce a lockfile?
Let's dive into the details of Python packaging: the past, the present, the challenges ahead, and the proposed solutions.
"Python packaging is a problem" is a meme. What is Python packaging? What is being packaged, where is it sent from, and where is its destination? Why, oh why, can't I just produce a lockfile? Let's dive into the details of Python packaging: the past, the present, the challenges ahead, and the proposed solutions.