-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[interactive] show all update prior to ask for all #72
Comments
Thank you for taking the effort to give feedback. I'm not sure I understand the issue. You would like to see all the possible updates, but you find |
Yes I expect same list. Of course I can do
With these 2 workflows we have to wait just once. Up to you. |
Thanks for the explanation. Pull requests and more opinions welcome. |
@sylvain-bougnoux I suddenly wondered. Doesn't |
Actually yes. The only issue is that you have to wait twice for pip-review to know what to do. One pip-review call takes for me about 20-30s to respond. It is awkward to have to wait twice. |
Ah, you mentioned the having to wait twice before. Sorry for overlooking that in my previous comment. I find the use case very reasonable. How about the following. Add a Please don't wait for me to implement it, though. See #76. I'll welcome a pull request that implements something like this. |
This is a feature I want even in It has less information and less real-time than the progress bar discussed in issue #77, but it seems easy to implement. And being presented with a list of what will be updated in advance gives you a sense of security that you are aware of the situation in either mode. If someone responds to this for both modes, would the option name be around |
pip-review -i
shows the 1st update and ask foryes, no, all, quit
. It would be convenient to show all possible updates prior to pressing 'A', because sometimes some packages must not be updated. If yes or no, only the 1st one will be treated. I understand I can callpip list -o
before, but it is a bit long with many packages.My 2c.
Thanks for this very useful tool anyway.
The text was updated successfully, but these errors were encountered: