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
Upgrading package reinstalls old version #2179
Comments
Thanks for the incredibly thorough report. It seems like |
Thanks for fast response, I was afraid all the time that I am doing something stupid and will find out just after I click Submit 😅 I have used |
- `pipenv update` currently doesn't actually run `pipenv lock` - Semantics around this changed but it doesn't look like the code did - `pipenv update` should operate similarly for all operations by running `lock` followed by `sync` - Fixes #2179 Signed-off-by: Dan Ryan <dan@danryan.co>
- `pipenv update` currently doesn't actually run `pipenv lock` - Semantics around this changed but it doesn't look like the code did - `pipenv update` should operate similarly for all operations by running `lock` followed by `sync` - Fixes #2179 Signed-off-by: Dan Ryan <dan@danryan.co>
Checked #1490 and other issued that mention update.
Upgrading package with
pipenv update PACKAGE
upgrades given PACKAGE but then reinstalls old version.$ python -m pipenv.help output
Pipenv version:
'11.10.4'
Pipenv location:
'/usr/local/lib/python3.6/site-packages/pipenv'
Python location:
'/usr/local/bin/python'
Other Python installations in
PATH
:2.7
:/usr/bin/python2.7
2.7
:/usr/bin/python2.7
3.6
:/usr/local/bin/python3.6m
3.6
:/usr/local/bin/python3.6
3.6
:/usr/local/bin/python3.6
3.6.5
:/usr/local/bin/python
3.6.5
:/usr/local/bin/python
2.7.9
:/usr/bin/python
2.7.9
:/usr/bin/python2
3.6.5
:/usr/local/bin/python3
3.6.5
:/usr/local/bin/python3
PEP 508 Information:
System environment variables:
HOSTNAME
GPG_KEY
SHELL
TERM
OLDPWD
PYTHON_VERSION
PATH
PWD
LANG
PYTHON_PIP_VERSION
SHLVL
HOME
_
PYTHONDONTWRITEBYTECODE
PIP_PYTHON_PATH
Pipenv–specific environment variables:
Debug–specific environment variables:
PATH
:/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
SHELL
:/bin/bash
LANG
:C.UTF-8
PWD
:/test
Contents of
Pipfile
('/test/Pipfile'):Contents of
Pipfile.lock
('/test/Pipfile.lock'):Expected result
Given I have
requests = "==2.17.0"
in Pipfile and I change it torequests = "*"
, runningpipenv update requests
I would expect to have latest version of requests.Actual result
Steps to replicate
requests = "==2.17.0"
withrequests = "*"
requests
requests
versionI found that if I run
pipenv lock
before step 4,Pipfile.lock
would be updated and everything would work as expected for me. Upgrade workflow does not mention need to lock before update.Please note that in my real project I have
"*"
version specified but I wouldn't be able to make reproducable case as it happend when new version of package is released.The text was updated successfully, but these errors were encountered: