-
-
Notifications
You must be signed in to change notification settings - Fork 611
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
Resolver error on package version change #2114
Comments
Could you include full file contents, not just parts of them? |
|
Does using |
Yes, but I do not want to upgrade packages unless necessary. My understanding is the same as in #1977 (comment). My intention is to maintain existing constraints when possible and only drop them if need be, which I believe is the intended behavior of |
Any update on this? |
Related issue: #1977
When changing the version of a pinned dependency in requirements.in with an existing requirements.txt that includes an unpinned dependency that must change, pip-compile fails with a resolver error.
Environment Versions
Steps to replicate
Expected result
Running
pip-compile
with the changed version fortorch
will automatically change thetorchvision
version to satisfy requirements.in instead of failing.The text was updated successfully, but these errors were encountered: