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"
-vvvoption) and have included the output below.Issue
The gist link contains a
pyproject.tomlfile and apoetry.lockfile. The tree structure of the project is:The file
__init__.pyis empty.Steps to recreate: Running
pip install .from the root directory in a fresh virtual enviroment respects the versioning specified inpyproject.toml, but not the versioning of the lock file. Specifically, it will installapache-beamversion 2.44.0 despite the lock file specifying version 2.42.0.Expected behaviour: I expect
pip install .to respect the lock file and installapache-beamversion 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.