The Evolutionary Saga of Python Packaging
summary
Timeline of concrete fixes not promises: setuptools adds dependency declarations and entry points; pip adds uninstall and HTTPS to PyPI; wheel standardizes binary filenames with OS/arch tags; virtualenv isolates interpreters; conda ships precompiled cross‑platform binaries and handles non‑Python deps; pipenv brings Pipfile, pyproject.toml and Poetry enable publishing; PDM and UV reimplement managers (UV in Rust). Still recurring failures include visual C++ 14.0 unspecified error and the binary problem that never fully goes away despite 450,000–500,000 monthly visits to early indexes.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:08Python packaging frustrates users
- 3:40Early Python package distribution
- 7:10Vaults of Parnassus era
- 8:15Python as glue language
- 10:43Rise of distutils and limits
- 12:07Setuptools revolution
- 14:53Eggs and easy_install era
- 16:16Virtualenvs and Python 3
- 17:21Pip and package management
- 18:27Wheels and binary distribution
- 20:57Anaconda and conda
- 22:41Pipenv and dependency management
- 24:03PEP 518 and pyproject.toml
- 25:28Poetry and PDM
- 26:33UV and future tools
- 27:37Why Python packaging will always be challenging
- 28:58Pyodide and web assembly
related talks
44mNobody Expects the Python Packaging Authority
24mInside the Cheeseshop:How Python Packaging Works
25mInside the Cheeseshop: How Python Packaging Works
32mInside the Cheeseshop: How Python Packaging Works
34mAdventures in pip land
36mPython Packaging from Init to Deploy
23mPackaging Python in 2021
45mThe Five Demons of Python Packaging That Fuel Our Persistent Nightmare