We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Zen of Python Dependency Management

Formal Metadata

Title
Zen of Python Dependency Management
Subtitle
Dependency resolution via pyproject.toml — replacing setup.py, requirements.txt, and MANIFEST.ini
Title of Series
Number of Parts
118
Author
License
CC Attribution - NonCommercial - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
Ensuring reliably repeatable dependency installation has long been an unsolved problem for many Python projects. Pinning dependencies via setup.py and requirements.txt has historically been met with extra work and unexpected results, particularly when managing the dependencies of dependencies. Thanks to PEP 518, Python projects can now more easily manage dependencies via the new pyproject.toml file specification. In its wake, a number of useful tools have arisen that use this file to provide enhanced dependency resolution, including Poetry, Hatch, and Pipenv. Attendees of this talk will take home the following knowledge and skills: how to replace three files (setup.py, requirements.txt, and MANIFEST.ini) with just one: pyproject.toml why dependency resolution is hard and why it matters how Poetry, Hatch, and Pipenv differ and when to use each why one might use a less magical alternative: pip-tools how to use pipx to isolate system-wide Python tools
Keywords