Skip to content

poetry instead of Pipfile #123

Closed
Closed

Description

@RCheese

subj

Activity

  1. jlugao commented on Mar 2, 2020

    @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

  2. RCheese commented on Mar 2, 2020

    @RCheese
    ContributorAuthor

    +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

  3. StephenBrown2 commented on Mar 2, 2020

    @StephenBrown2
    Contributor

    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
    
  4. RCheese commented on Mar 2, 2020

    @RCheese
    ContributorAuthor

    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)

  5. laurentS commented on Mar 19, 2020

    @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.

  6. lucawen commented on Apr 6, 2020

    @lucawen

    this will be really great and simple to change!

  7. tiangolo commented on Apr 13, 2020

    @tiangolo
    Member

    Yep. I want to migrate this to Poetry 😄

    I just haven't had the time yet.

  8. mrbox commented on Apr 15, 2020

    @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 ...?

  9. tiangolo commented on Apr 18, 2020

    @tiangolo
    Member

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

    Thanks @RCheese for the idea and PR!

  10. added a commit that references this issue on Dec 19, 2024
  11. added a commit that references this issue on Mar 27, 2025
  12. added a commit that references this issue on Jul 31, 2025
  13. added a commit that references this issue on Aug 4, 2025
  14. added a commit that references this issue on Oct 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions