-
-
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
Pipenv install --selective-upgrade #4351
Comments
I have been having this issue and have found a workaround.
The only downside is that it seems to add the new hashes and keeps the old ones, but that doesn't seem too big of a deal to me. This comment clarifies some things: |
|
Issue description
Attempting just to upgrade one package, with out updating other packages.
Steps to replicate
Git clone - https://github.com/saisankargochhayat/pipenvTest
Couple of scenarios I tried out just to update one package requests -
pipenv install requests==2.24.0 --keep-outdated
Just updates the package version, but not the hashes in the Pipfile.lock, pins down in Pipfile
pipenv install --selective-upgrade requests==2.24.0
Just updates the package version, but not the hashes in the Pipfile.lock, pins down in Pipfile
pipenv install requests==2.24.0
Updates both requests and semver to their latest versions and the hashes.
pipenv update --selective-upgrade requests
Updates both requests and semver to their latest versions and the hashes.
Seems like
pipenv install {dependency}=={package_version} --keep-outdated
earlier did the trick, but now it works, but just misses out on the new hash. Is there a new way to achieve this?Pipenv support output - https://gist.github.com/saisankargochhayat/a7d09bdc1cea8eeadf902a1bae503b1d
The text was updated successfully, but these errors were encountered: