Repository navigation
[build-system] requires does not fail on mismatch #2856
Description
- I am on the latest Poetry version.
- I have searched the issues of this repo and believe that this is not a duplicate.
- If an exception occurs when executing a command, I executed it again in debug mode (
-vvvoption).
- macOS:
- 1.0.10:
- pyproject.toml:
...
[build-system]
requires = ["poetry==1.0.10"]
build-backend = "poetry.masonry.api"
Issue
I am attempting to pin to a specific version of poetry in Docker and in the pyproject.toml, but it does not fail when installing while using a mismatching poetry version.
In this case, I've updated the pyproject.toml file to 1.0.10, and am using 1.0.9 locally.
Activity
abn commentedon Aug 27, 2020
@aethanol I think you are misunderstanding PEP 517 here. The purpose for this is it allow build system to determine what build backend to use when building a package. For example if you install a poetry managed managed project using pip or any other PEP 517 compatible build front ends, eg:
pip install /path/to/packageorpip install source.tar.gzetc. In these example pip will create a new isolated temporary build environment with thebuild-system.requirespresent along with the source and call thebuild-backendmethod to produce awheelorsdistit can install to the active environment. Poetry itself does not take this into account for poetry managed projects.This is not intended to control the version of poetry made available to the user in their enviornment. This is should be managed outside the context of the project.