pin poetry-core version to <2.0.0 in pyproject.toml #3025
Merged
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.
got back from christmas vacation and rebuilt our framework that uses locust as a library for the first time, and running it failed:
scratching my head abit, but realised it thought it was probably related to
poetry-dynamic-versioning
, so saw that there had been a new release 2025-01-04, but inpyproject.toml
this has been pinned with<2.0.0
, butpoetry-core
had a broader constraint and a 2.x version had been released 2025-01-04 as well.looking through the commit history I found:
81116b2 - Pin Poetry verison in one more place.
fcb6104 - Pin Poetry to 1.x
adding a
<2.0.0
constraint inpyproject.toml
forpoetry-core
solved the issue when usinglocust
as a library.