duplicate entry in poetry.lock in 2.1.1

[jouve]

with the following dependencies,

[tool.poetry.dependencies]
python = "^3.10"
ansible-core = "*"
hvac = "*"
kubernetes = "*"
openstacksdk = "*"
pydantic = "*"
python-dateutil = "*"

[tool.poetry.group.dev.dependencies]
ansible-dev-tools = "*"
ansible-lint = { version = "*", markers = 'platform_system!="Windows"' }
epdb = "*"
ipython = "*"
petname = "*"
pyright = { version = "*", extras = ["nodejs"] }
pysocks = "*"
python-neutronclient = "*"
python-openstackclient = "*"
ruff = "*"
types-python-dateutil = "*"
types-urllib3 = "*"

[tool.poetry.group.docs.dependencies]
antsibull-docs = "*"
sphinx-ansible-theme = "*"

poetry generate 2 [[package]] entries for ansible-core

[[package]]
name = "ansible-core"
version = "2.17.9"
description = "Radically simple IT automation"
optional = false
python-versions = ">=3.10"
groups = ["main", "dev"]
markers = "python_version < \"3.12\""
files = [
    {file = "ansible_core-2.17.9-py3-none-any.whl", hash = "sha256:d2fde719fa8bcaa303ae9b289099c4d49d6566d06e233a47b01de0d4e5438f7b"},
    {file = "ansible_core-2.17.9.tar.gz", hash = "sha256:c24cdc2bab19b910bbdb4a1074af5745e16c78c618f15829e7ddcf699f69a510"},
]

[package.dependencies]
...

[[package]]
name = "ansible-core"
version = "2.18.3"
description = "Radically simple IT automation"
optional = false
python-versions = ">=3.11"
groups = ["main", "dev"]
markers = "python_version >= \"3.12\""
files = [
    {file = "ansible_core-2.18.3-py3-none-any.whl", hash = "sha256:4d5120916b6d36881185c0c7231cdb7b1675f7dddd1a7a833a7d67d56bcdfcc8"},
    {file = "ansible_core-2.18.3.tar.gz", hash = "sha256:8c4eaca40845238e2601b9bc9dbfbd4f6ed3502cb8b2632789f75ce478abfdee"},
]

[package.dependencies]
...

the difference being in version, python-versions & markers:

version         | "2.17.9"                    | "2.18.3"
python-versions | ">=3.10"                    | ">=3.11"
markers         | "python_version < \"3.12\"" | "python_version >= \"3.12\""

is this a new expected behavior ?

[guillermodotn]

I’m not sure if it’s a new behavior, but to me, Poetry 2.1.1 doesn’t behave like that. I’d say your poetry.lock file is in the correct format, but when trying to reproduce it with the same dependencies and pinned versions, and using a python3.13.2 environment, Poetry resolves the ansible-core dependency to version 2.17.9, which, as stated in the Ansible docs, does not support that Python version.

Can you please provide some insights about your environment, such as the Python versions available in the PATH and the commands you usually use to create/setup your Python environment?

[jouve]

my environment is a devcontainer

• mcr.microsoft.com/devcontainers/base:1.2.3-jammy,
• system python 3.10,
• poetry installed with pipx

[jouve]

reverting to poetry 2.0.1 removes the duplicate entry (same as above except pipx install 'poetry<2.1.0')

[guillermodotn]

The second entry of ansible-core in this case seems to be a dependency.
If you remove the dev packages:

ansible-dev-tools = "*"
ansible-lint = { version = "*", markers = 'platform_system!="Windows"' }

erase poetry.lock, and generate it again, the dependency disappears.

However, in your specific environment, ansible-core == 2.18.3 is not installed. You can verify this with:

poetry run pip list | grep ansible-core

It seems that poetry.lock creates [[package]] entries for dependencies of dependencies.

[jouve]

yes, I can also specifiy "<2.18" in the tool.poetry.dependencies.

My questioning is if this is an intentionnal evolution, a bugfix or a regresssion in poetry>2.1.0

[radoering]

In general, it is not a bug to have more than one entry per package. That had already been the case with Poetry 1. With Poetry 2, you can even see that the two entries are mutually exclusive (if they are not that would be a bug): The first entry is for Python < 3.12 and the second entry is for Python >= 3.12.

Disclaimer: I did not check if the two entries in this use case are correct or why/if there are two entries with Poetry 2.1 and only one entry with Poetry 2.0.

[jouve]

thanks for the clarification :)

[jouve]

Out of curiosity, I was looking at how uv behave in the same context.

The default behavior is identical to poetry 2.1, but changing fork-strategy to fewest, it locks only 1 version of ansible-core (like poetry 2.0).