Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add "upgrade" and "upgrade-all" commands
See original GitHub issue(Updated to reflect reality in April 2020)
This issue was initially scoped for changing the behavior of pip install --upgrade, by adding a new upgrade command with a different behavior when upgrading packages. The older recursive “eager” default caused grief for many (#304) However, after a lot of discussion on this, the approach taken was to add the --upgrade-strategy flag. The flag initially had a default of “eager” which was changed to a better default in #4500.
The tracking issue for “upgrade all packages” functionality is #4551.
Issue Analytics
- State:
- Created 13 years ago
- Reactions:194
- Comments:251 (149 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Are you going to implement this in next 10 years?
pip install --upgrade :all:is extremely weird. Let’s stick to POSIX semantics, which basically everyone is doing nowadays:pip install --upgrade --all