The Real Python Podcast

Going Beyond requirements.txt With pylock.toml and PEP 751

50 snips
May 16, 2025
Brett Cannon, a Python Core Developer and packaging expert, joins to discuss his journey with PEP 751 and the new pylock.toml format. He highlights the importance of evolving beyond requirements.txt for better dependency management. Cannon shares insights into the influence of lock files on project reproducibility and the collaborative challenges faced by the Python community in standardizing practices. He also reflects on the historical shift toward security-focused packaging, showcasing the growth in Python's ecosystem.
Ask episode
AI Snips
Chapters
Transcript
Episode notes
ANECDOTE

Brett's Long Packaging Journey

  • Brett Cannon has been working on improving Python dependency management for over six years.
  • His previous PEP 665 was rejected, but he continued persistence leading to PEP 751 acceptance.
INSIGHT

Limitations of requirements.txt

  • The requirements.txt format isn't a formal specification but a pip-specific implementation.
  • This causes tooling inconsistencies since many tools export but don't consume requirements.txt files.
INSIGHT

Success of pyproject.toml

  • Pyproject.toml succeeded because it provided a unified specification for project metadata.
  • It became the baseline file for supporting various tools to work consistently.
Get the Snipd Podcast app to discover more snips from this episode
Get the app