python-poetry / python-poetry/poetry
`poetry lock --no-update` still updates dependencies
Open
Nobody has claimed this yet.
kind/feature
status/triage
- Dominant language
- Python
- Stars
- 34.3k
- Forks
- 2.5k
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 30
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:
- Poetry version:
- Link of a Gist with the contents of your pyproject.toml file:
https://gist.github.com/tobi-lipede-oodle/2954049e777c9b0178209a7fc3a75858
Issue
To recreate, you can run:
pip install requests==2.25.1
poetry lock --no-update
# Updating dependencies
# Resolving dependencies... (39.6s)
I would expect that after running the commands above, I should just see Resolving dependencies... and my lockfile would just have requests 2.25.1. However, what I actually see is that requests gets updated to 2.26.0.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the commands in the issue with the linked pyproject.toml and compare the resulting lockfile, including the requests version. Then trace the implementation of poetry lock --no-update and its dependency resolution behavior; done means the command preserves requests 2.25.1 as expected and the relevant tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100