Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Check List
Resolves: #3527
My comments
I have tried to follow the suggestion from here to come up with an solution. From what I have observed, it does not result in a resolution using the lowest version, but behaves the same as
strategy=highest
.To reproduce, run
poetry install
then the dev version should be available at.venv/bin/poetry
.Try lock with an experiement project (e.g. with only one dependency, say
requests
):Then check what the result is, by
poetry show --directory xyz
(either using the dev one or a prod one):That means the native approach does not work. As a next step, I would have a deeper look at
version_solver.py
to understand if we could change the heuristics on version solving (not sure if I need to fully understand the Pubgrub algo though).