-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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.
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
Pip install does not respect poetry.lock
#7419
Comments
poetry-core does not currently understand poetry.lock, this is known and expected behaviour python-poetry/poetry-core#83 is the last try I know of at making it happen |
Thanks, I see. Is this referenced anywhere in the docs? Here it is mentioned that poety-core reads lock files which we interpreted exactly as poetry.lock is understood by poetry-core.
|
I dunno, I'm sure you can search the docs as well as I can! merge requests improving them should be welcome |
Duplicate #2778 |
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. |
-vvv
option) and have included the output below.Issue
The gist link contains a
pyproject.toml
file and apoetry.lock
file. The tree structure of the project is: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 inpyproject.toml
, but not the versioning of the lock file. Specifically, it will installapache-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 installapache-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.The text was updated successfully, but these errors were encountered: