Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Stop using poetry as a build backend #121

Closed
supakeen opened this issue Apr 20, 2022 · 3 comments
Closed

Stop using poetry as a build backend #121

supakeen opened this issue Apr 20, 2022 · 3 comments
Assignees
@supakeen
Labels
enhancement New feature or request
Milestone
1.4.0

Comments

@supakeen
Copy link
Owner

Due to some concerns listed in python-poetry/poetry#3332 poetry does not as of yet support the PEP-621 form of shared metadata information.

As I want to be able to more easily switch build backends in the future let's switch to the pip build backend.
@supakeen supakeen added the enhancement New feature or request label Apr 20, 2022
@supakeen supakeen added this to the 1.4.0 milestone Apr 20, 2022
@supakeen supakeen self-assigned this Apr 20, 2022
@CAM-Gerlach
Copy link

Just FYI—pip is a build frontend, not a backend. Setuptools, flit_core, Hatchling, pdm and poetry are all build backends (though some also offer build frontends too, at least for their own build system).

@supakeen
Copy link
Owner Author

Ah, thanks for the clarification :)

@supakeen
Copy link
Owner Author

supakeen commented Jun 3, 2023

Done and switched to pdm.

@supakeen supakeen closed this as completed Jun 3, 2023
NeilHanlon added a commit to neil-forks/pinnwand that referenced this issue Oct 27, 2023
@NeilHanlon
use project.scripts instead of tool.poetry.scripts for entrypoints
e1772a7 
After the change from poetry to pdm in supakeen#121, it appears that some build systems
have trouble groking what scripts to install due to the use of the
poetry-specific entrypoint configuration in pyproject.toml.

This change updates the pyproject.toml to use the
[PEP-621](https://www.python.org/dev/peps/pep-0621) specification for
identifying console_scripts/entrypoints, and resolves the build issue on
Fedora. From my testing, there is no impact for installations via e.g.
`pip`, as these tools will understand PEP-621 entrypoint specifications.
@NeilHanlon NeilHanlon mentioned this issue Oct 27, 2023
Merged
supakeen pushed a commit that referenced this issue Oct 28, 2023
@NeilHanlon @supakeen
use project.scripts instead of tool.poetry.scripts for entrypoints
7868b4b 
After the change from poetry to pdm in #121, it appears that some build systems
have trouble groking what scripts to install due to the use of the
poetry-specific entrypoint configuration in pyproject.toml.

This change updates the pyproject.toml to use the
[PEP-621](https://www.python.org/dev/peps/pep-0621) specification for
identifying console_scripts/entrypoints, and resolves the build issue on
Fedora. From my testing, there is no impact for installations via e.g.
`pip`, as these tools will understand PEP-621 entrypoint specifications.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@supakeen supakeen

Labels
enhancement New feature or request
Projects
None yet
Milestone
1.4.0
Development

No branches or pull requests
2 participants
@CAM-Gerlach @supakeen