poetry instead of Pipfile

[RCheese]

subj

[jlugao]

+1 on poetry, however, I am not sure how to go about deployment with it, might have to generate a requirements.txt for that

[RCheese]

+1 on poetry, however, I am not sure how to go about deployment with it, might have to generate a requirements.txt for that

Poetry might generate requirements.txt out of the box since 1.0 version for docker install or PyCharm indexing and etc. In case of pipfile you need a another tool as requirementslib for this

[StephenBrown2]

Like @RCheese said (but with links), Poetry 1.x will generate a requirements.txt:
https://python-poetry.org/docs/cli/#export

poetry export -f requirements.txt > requirements.txt

[RCheese]

Poetry 1.x will generate a requirements.txt:
https://python-poetry.org/docs/cli/#export

poetry export -f requirements.txt > requirements.txt

I wrote the same)

[laurentS]

I have modified my project to use poetry, and I changed the dockerfiles to do the following:

COPY ./backend/app/pyproject.toml ./backend/app/poetry.lock /app/
RUN cd /app && $HOME/.poetry/bin/poetry config virtualenvs.create false && $HOME/.poetry/bin/poetry install

The config virtualenvs.create false part disables the use/creation of a venv by poetry, so it installs everything in the "main" python inside the docker images. While not required, I feel that using the same tool everywhere makes more sense.

As a side note, I use a custom base image with most of my python dependencies in it to save time in CI, and there is a bug in poetry that reinstalls everything even if included in the base image, but it still works.

[lucawen]

this will be really great and simple to change!

[tiangolo]

Yep. I want to migrate this to Poetry 😄

I just haven't had the time yet.

[mrbox]

I'll create a PR for this, most likely this week. @tiangolo what do you think about also changing backend.dockerfile to install dependencies using Poetry instead of raw pip install ...?

[tiangolo]

We now have Poetry, and it's integrated into the Dockerfiles as well. 🚀

Thanks @RCheese for the idea and PR!