-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
install's --keep-outdated
does not seem to be respected
#1554
Comments
the lockfile will always get re-generated if it is out-of-date. |
@kennethreitz Can you clarify what the intent of My goal here is to find a method to install a new dependency without updating the world, which is what it looked like this flag was for based on the discussion at #1255. |
use |
That doesn't work. If I do the same repro steps as above except substituting |
Ping @kennethreitz, what is the expected behavior here? The flag doesn't seem to do anything and the docs don't say much. |
Have tried |
This is still an issue -- can we reopen? I just converted my git links from IMO, |
and we have another issue open tracking |
@techalchemy which issue/PR is that? Nothing open I see now seems appropriate. |
I'm running into the same issue, |
For those following along at home, it seems like this flag is indeed legitimately broken. From #966 (comment):
This issue should probably be re-opened to reflect reality. |
Also looking for solution for more selective upgrade, not doing the .lock stuff by hand after each update :/ |
Why is this closed? The issue is still present... It isn't possible to update one package without updating all packages. If you have lots of dependencies, you'll wait a few minutes just to see that pipenv upgraded packages and introduced a conflict. |
This issue ranks pretty highly on Google searches for "pipenv keep-outdated", so I've added the references to the open issues to the original post (otherwise folks may think the issue has been closed because it is working as expected, when it has actually been closed as a duplicate of an existing issue & PR). |
(Closed as duplicate, see issue at #966 and PR at #3304)
When I have outdated dependencies, installing a new package with the
--keep-outdated
flag still updates dependencies that have no overlap with my newly-requested dependency. Similar issues (but pre---keep-oudated
, I think?): #966, #1219, #1409.Describe your environment
Expected result
Packages that have no overlap in their dependencies with my current set of dependencies should not change my current set of dependencies when
--keep-outdated
is specified.Actual result
My existing packages are updated as if I had not specified the flag.
Steps to replicate
Pipfile pre-coverage, pre-editing
Pipfile pre-coverage, post-editing
Pipfile.lock pre-coverage
Pipfile post-coverage
Pipfile.lock post-coverage
The text was updated successfully, but these errors were encountered: