Repository navigation
Incorrect locking of platform-specific wheel dependencies #4810
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).
- OS version and name: Debian 11
- Poetry version: 1.1.1 / 1.2.0a2
- Link of a Gist with the contents of your pyproject.toml file: https://gist.github.com/nyuszika7h/3b26db37f0cdfe6ecc7f5bd9e2522c06
Issue
When given the above pyproject.toml file, running poetry lock on Linux generates the following poetry.lock:
[[package]]
name = "test"
version = "1.0"
description = ""
category = "main"
optional = false
python-versions = "*"
[package.source]
type = "file"
url = "wheels/test-1.0-cp34-abi3-win_amd64.whl"Also, poetry export outputs:
test @ file:///home/nyuszika7h/example/wheels/test-1.0-cp34-abi3-win_amd64.whl; sys_platform == "win32" or sys_platform == "linux" or sys_platform == "darwin"
The expected behavior would be to include 3 separate entries, one for each platform.
Interestingly enough, poetry install is smart enough to pick the correct version for the platform despite the incorrect locking. But the lock file is incomplete, and the requirements.txt output is just completely wrong.
Activity
teaVeloper commentedon May 11, 2022
I also have a similar issue with
poetry 1.2.0b1locking some dependencies as windows and creating arequirements.txtmentioning windows, and thus install failed on a system I can only userequirements.txt-poetry 1.1.13did resolve the samepyproject.tomlcorrectly.If helpful, I can create an Issue for that with more details.
github-actions commentedon Mar 1, 2024
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.