Repository navigation
Lightweight core library #1993
Description
Currently, to build a Poetry project via the PEP-517 build mechanism, you need this section:
[build-system]
requires = ["poetry>=1.0.3"]
build-backend = "poetry.masonry.api"This works but this has the undesirable side-effect of pulling the full Poetry stack and its dependencies. Most of them are not needed to build the project and expose the metadata.
To prevent that, we need to extract parts of the Poetry stack into a more lightweight library with the sole purpose of building projects.
Ideally, this core library should not have any dependency to avoid errors to to circular build dependencies when using pip install --no-binary :all:.
Reacted by Jan Hermann, sinoroc, finswimmer, Aaron Jheng, André Sassi, James Myatt, Claudio Jolowicz, Adithya Balaji, Ülgen Sarıkavak, Rafal Krupinski and 7 more
Reacted by Ülgen Sarıkavak, Guilhem Saurel and Ryan Sobol
Activity
pradyunsg commentedon Mar 2, 2020
Just to be sure, this core would be analogous to
flit_core, correct?sdispater commentedon Mar 20, 2020
@pradyunsg Yes, the idea is to not require the full Poetry stack just to build projects.
And it will help fix the issue with
pipwhen there are cyclic dependencies between the build backend and its own dependencies.ulgens commentedon Apr 30, 2020
@sdispater Isn't this resolved by #2212 ? Not sure why this one is not automatically closed. Also, we can mark it as done on #1856 .
github-actions commentedon Mar 3, 2024
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.