-
Notifications
You must be signed in to change notification settings - Fork 12
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
How to selectively upgrade dependencies? #19
Comments
I believe it already does it by default. |
Interesting. 🤔 That's great to hear, but I was sort of expecting that a resolver used by pipenv would have to also support the upgrade-everything workflow, per discussions on that same issue. I imagine, though, since you mentioned "by default" a couple times, there's a way to override this to eagerly upgrade everything? |
Yeah there are currently two “strategies” you can choose from the command line, “eager” and “only-if-needed”. https://github.com/sarugaku/passa/blob/master/src/passa/cli/upgrade.py#L25 If you don’t choose one, only-if-needed is used (hence “by default”). The difference if that say if package A depends on B, (The idea is borrowed from |
The reminds me, there really needs some write up on how the whole system is designed… |
Per @techalchemy 's comment on this (now locked) issue: pypa/pipenv#966 (comment)
I would love to help test this out, but it's not clear to me from the docs here how to test the workflow where I only want to upgrade dependencies (and their dependencies) that are necessary to the current operation (e.g. upgrading a top-level dependency). Does passa also support
--selective-upgrade
or--keep-outdated
, or is there some other way of achieving similar behavior?The text was updated successfully, but these errors were encountered: