You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to have a poetry check command for the virtual environment that basically does poetry install --sync --dry-run with the following changes:
Prints only the summary Package operations: 1 install, 0 updates, 0 removals, 56 skipped
Exit 0 if no operations would have been done
Exit 1 otherwise
This was requested in #3599 as well but was dropped due to lack of interest.
I can try to create a Pull Request but I'd need some guidance regarding calling the Executor from check command. It's probably easier to implement it in poetry install but it feels wrong from a UX perspective.
Impact
This feature can be used in a pre-commit post-checkout and post-merge hook to notify a developer if their current virtual environment isn't up to date. It saves troubleshooting time when other developers update dependencies and your current venv isn't up to date.
It also doesn't force the developer to use the workaround mentioned below that forces the developer to always scroll again to see the relevant output.
Workarounds
You can use this snippet, but it prints all the dependencies and doesn't exit with a failure reason.
Issue Kind
Brand new capability
Description
I'd like to have a
poetry check
command for the virtual environment that basically doespoetry install --sync --dry-run
with the following changes:Package operations: 1 install, 0 updates, 0 removals, 56 skipped
This was requested in #3599 as well but was dropped due to lack of interest.
I can try to create a Pull Request but I'd need some guidance regarding calling the Executor from check command. It's probably easier to implement it in poetry install but it feels wrong from a UX perspective.
Impact
This feature can be used in a pre-commit post-checkout and post-merge hook to notify a developer if their current virtual environment isn't up to date. It saves troubleshooting time when other developers update dependencies and your current venv isn't up to date.
It also doesn't force the developer to use the workaround mentioned below that forces the developer to always scroll again to see the relevant output.
Workarounds
You can use this snippet, but it prints all the dependencies and doesn't exit with a failure reason.
The text was updated successfully, but these errors were encountered: