requirements.txt is not good enough for managing Python dependencies; use Poetry instead
My response to the discussion topic posed in Python Packaging Strategy Discussion Part 1 had become quite long, so I decided to move it to write a blog post instead. This post then started absorbing various draft posts I’ve had on this topic since this blog was started, morphing to include my broader thoughts on where we are today. Note: I’ve updated this to cover an aspect of the recent LWN article on the topic as well.
requirements.txt is not good enough for managing Python dependencies; use Poetry instead
requirements.txt is not good enough for managing Python dependencies; use Poetry instead
You keep using that word. I don’t think it means what you think it means.
Explaining the basic concepts and best practices for creating Python packages in early 2023 using pyproject.toml build standards.
Frost Ming's personal blog