Skip to content
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

poery lock --no-update drops required locked packages #5434

Closed
3 tasks done
radoering opened this issue Apr 9, 2022 · 1 comment · Fixed by #5435
Closed
3 tasks done

poery lock --no-update drops required locked packages #5434

radoering opened this issue Apr 9, 2022 · 1 comment · Fixed by #5435
Labels
kind/bug Something isn't working as expected

Comments

@radoering
Copy link
Member

  • 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 (-vvv option).
  • OS version and name: any
  • Poetry version: 1.2.0b1
  • Link of a Gist with the contents of your pyproject.toml file:

Issue

Given the following pyproject.toml from #5141

[tool.poetry]
name = "poetry-test"
version = "0.1.0"
description = ""
authors = ["Glenn Matthews <[email protected]>"]

[tool.poetry.dependencies]
python = "^3.6"
celery = [
    {version = "~5.1.0", python = "<3.7"},
    {version = "~5.2.0", python = ">=3.7"},
]

[build-system]
requires = ["poetry-core>=1.0.0"]
build-backend = "poetry.core.masonry.api"

when running poetry lock and afterwards poetry lock --no-update, some required packages are dropped from the lock file.
For example click-didyoumean 0.0.3 is dropped although required for python 3.6.0, because the other entry for click-didyoumean (0.3.0) requires python_version >=3.6.2.

This issue also impacts exporting a requirements.txt via poetry-plugin-export.

@radoering radoering added kind/bug Something isn't working as expected status/triage This issue needs to be triaged labels Apr 9, 2022
@abn abn closed this as completed in #5435 Apr 10, 2022
@mkniewallner mkniewallner removed the status/triage This issue needs to be triaged label Jun 11, 2022
Copy link

github-actions bot commented 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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Something isn't working as expected
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants