Packaging Python in 2021
summary
Claims that pyproject.toml is now a final standard and that setup.py is becoming unnecessary, shows concrete examples of declaring a build backend and a three-line legacy fallback, and explains the PEP 518 fix for the confusing bdist_wheel pip error by adding wheel or build-system.requires. Names actual tools used: pip, setuptools, wheel, black, isort, and the front-end/back-end separation, recommends moving metadata into setup.cfg and removing setup.py once build metadata lives in pyproject.toml.
AI-written summary · about
chapters (10)
- 0:00Start
- 2:09Extra Configuration
- 3:18Anatomy of pyproject.toml
- 4:37Builder Flow
- 8:23Genesis of Builders
- 9:46Evolution of Builders
- 11:30Evolution of Installers
- 12:56Packaging Future
- 18:46Migrating an existing project
- 22:07Resources
related talks
28mModern Python packaging without pain
30mThe Evolutionary Saga of Python Packaging
26mWhat does PEP 517 mean for packaging
26mOpen Source on Easy Mode
44mNobody Expects the Python Packaging Authority
22mPublishing well formed Python packages
30mModernizing Your Python Package with pyproject and hatch
30mHow to give your Python code to someone else