Pip install does not respect poetry.lock #7419
Description
- Poetry version: 1.3.2
- Python version: 3.9.13
- OS version and name: Mac OS Monterey 12.2.1
- pyproject.toml: Link to gist containing toml file
- I am on the latest stable Poetry version, installed using a recommended method.
- I have searched the issues of this repo and believe that this is not a duplicate.
- I have consulted the FAQ and blog for any relevant entries or release notes.
- If an exception occurs when executing a command, I executed it again in debug mode (
-vvvoption) and have included the output below.
Issue
The gist link contains a pyproject.toml file and a poetry.lock file. The tree structure of the project is:
.
├── poetry-test
│ └── __init__.py
├── poetry.lock
└── pyproject.toml
The file __init__.py is empty.
Steps to recreate: Running pip install . from the root directory in a fresh virtual enviroment respects the versioning specified in pyproject.toml, but not the versioning of the lock file. Specifically, it will install apache-beam version 2.44.0 despite the lock file specifying version 2.42.0.
Expected behaviour: I expect pip install . to respect the lock file and install apache-beam version 2.42.0. My understanding (based on the information in here) is that this is part of what the following block from the toml file allows us to do.
[build-system]
requires = ["poetry-core"]
build-backend = "poetry.core.masonry.api"