Skip to content

Insufficient cache invalidation after Poetry upgrade causes lockfile diffs #7224

@intgr

Description

@intgr
  • Poetry version: 1.3.1
  • Python version: 3.11.1
  • OS version and name: Linux & macOS
  • pyproject.toml: (empty)
  • I am on the latest stable Poetry version, installed using a recommended method.
  • I have searched the issues of this repo and believe that this is not a duplicate.
  • I have consulted the FAQ and blog for any relevant entries or release notes.

Issue

I understand it must be convenient to close bugs, pretend they don't exist and ignore any follow-up comments like in #7207. But I spent at least two hours debugging this, so it would be a shame to lose this effort.

When I first install pynacl with Poetry 1.2, then upgrade to Poetry 1.3.1 and install the same package, the lockfile differs from what a fresh Poetry 1.3.1 installation would produce.

You can try these commands for example with Docker docker run -it --rm python:3.11.1 bash

Fresh installation

mkdir test
cd test
pip install poetry==1.3.1
poetry init -n
poetry add pynacl

Output:

root@f283c78a5680:/test# grep sphinx poetry.lock
docs = ["sphinx (>=1.6.5)", "sphinx-rtd-theme"]

Upgraded installation

mkdir test
cd test
pip install poetry==1.2.2
poetry init -n
poetry add pynacl
grep sphinx poetry.lock
rm poetry.lock

pip install poetry==1.3.1
poetry --version
poetry lock
grep sphinx poetry.lock

Output:

root@c14aa5d02d26:/test# grep sphinx poetry.lock
docs = ["sphinx (>=1.6.5)", "sphinx_rtd_theme"]

Workaround

The issue can be worked around with poetry cache clear --all .

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugSomething isn't working as expectedstatus/triageThis issue needs to be triaged

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions