Have you ever been into an issue where you wrote a program you created a “requirements.txt” file and wrote down all the required packages in the requirements.txt file but when you tried to move the pr...

Materialize

Bobby Iliev

DevOps

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

Learn about Poetry, a package dependencies management tool for Python that solves package dependency issues. Install Poetry using pip and create a Python project using Poetry.

Time to Ditch Requirements.txt now! Start using Poetry. Python Poetry Example

Let’s make our life easier with Poetry Python

Create a Python project by using Poetry Python

Handling Virtual Environment Using Poetry

Download Premium Poetry Cheatsheet for FREE 👇

Yeah, we are using poetry for our production API. Initially we thought that it’s cool idea, but apparently, it’s not that simple. 
For example, building Dockerfiles is a giant problem. If you are not going to commit your lock file, installing dependencies will take forever (~20 minutes for us). Second problem is that dependencies are installed into hidden venv, which you need to solve by either tricking poetry into installing dependencies globally by disabling virtualenvs, using multi-stage (<a href="https://github.com/python-poetry/poetry/issues/1178" target="_blank" rel="noopener nofollow">https://github.com/python-poetry/poetry/issues/1178</a>) or exporting deps into requirements.txt anyway. 
And it gets even worse if you want to deploy to the server instead of dealing with docker. Now you need to setup CI/CD pipeline to export deps, then build package if you are whl/module setup enjoyer, install it on the server using pip and deal with relocking and reinstalling half of the server deps if something is changed in you <code>pyproject.toml</code>. 
But maybe I’m missing something, and this can be done differently.

Good stuff! It’s nice seeing Python move in a more standard, package-based direction