Use poetry-core from master as the build system #4567

Activity

1. kmorrisCAL commented on Oct 29, 2021

   

   kmorrisCAL

   on Oct 29, 2021

   Last edited by kmorrisCAL

   More actions

   +1 on this issue/question.

   I also tried installing both poetry and poetry-core from their respective master branches, and the &subdirectory=mysubdir parameter was not honored.

   👍React with 👍1Reacted by Stephen Franklin
2. stinodego commented on Jan 9, 2022

   

   stinodego

   on Jan 9, 2022

   Last edited by stinodego

   More actions

   So how can I specify the build-system in my pyproject.toml to use the latest poetry-core i.e from its master branch.

   @sinoroc answered this question in issue #3419:

   [build-system]
   requires = ["poetry-core @ git+https://github.com/python-poetry/poetry-core.git"]
   build-backend = "poetry.core.masonry.api"

   I remember having an issue where I needed the master branch of the build system, and the above helped me.

   A few months late, but hopefully it helps anyone who lands on this issue.

   EDIT: Thanks for the correction! Updated in my post as well for those who won't read and just copy paste the first code they see 😄

   👍React with 👍2Reacted by sinoroc and Edgar Ramírez Mondragón
3. ashnair1 commented on Jan 11, 2022

   

   ashnair1

   on Jan 11, 2022

   Last edited by ashnair1

   ContributorAuthor

   More actions

   Brilliant. Thanks @stinodego. Minor correction regarding the link. It should be

   [build-system]
   requires = ["poetry-core @ git+https://github.com/python-poetry/poetry-core.git"]
   build-backend = "poetry.core.masonry.api"

   Side note:
   This does allow you to install dependencies (rooted in subfolders) but not manage them. I'm guessing poetry needs to be updated to do so. But if you add the dependency manually to pyproject.toml you can install it (from source and from .tar.gz).
4. ashnair1

   closed this as completedon Jan 11, 2022
5. github-actions commented on Mar 2, 2024

   

   github-actionsBot

   on Mar 2, 2024 – with GitHub Actions

   More actions

   This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
6. github-actions

   locked as resolved and limited conversation to collaborators on Mar 2, 2024