fix: updating poetry.lock before local wheels are used in solution template #495
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.
It is considered as a good practice that whenever you change the
pyproject.toml
file, you should runpoetry lock --no-update
afterwards to sync thepoetry.lock
files with those changes. This is what we do when some packages are provided as wheel files through thesetup_environment.py
. The--no-update
flag tries to preserve existing versions of dependencies.In this PR I am executing
poetry lock --no-update
as part ofsetup_environment.py
before installing dependencies.