-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
pip3 not upgrading a dependency #6457
Comments
Does passing the eager strategy work? (sorry for the terseness, heading to bed) |
No, it does not matter. |
@pradyunsg it works for me with |
heilaaks
added a commit
to heilaaks/snippy-tldr
that referenced
this issue
Mar 12, 2020
The Python 3.4 installation was failing locally with error related to 'BadZipfile: File is not a zip file'. The reason for this is unknown. This should work because the Snippy is able to install with the Python 3.4 and most of the Python modules are the same. This was not failing in Travis CI with Python 3.4. This workaround is now forced from the Makefile to allow exactly the same installation command to work with all the Python versions. [1] Add Makefile parameter to define PIP proxy, cache and upgrade parameters. The --upgrade-strategy option is now set by default to the 'eager'. There is a problem with the Snippy being installed from the Git. If there is already for example an version '0.10.0' from Snippy, the --upgrade option does not enforce upgrade to the version from the Git master branch. [2] [3] [1] https://stackoverflow.com/a/41916324 [2] https://pip.pypa.io/en/stable/reference/pip_install/ [3] pypa/pip#6457 (comment) Signed-off-by: Heikki Laaksonen <laaksonen.heikki.j@gmail.com>
Merging this into #5780 (comment)
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Environment
Description
It looks like some reports in comments in #2837 are true. Even if
setup.py
contains a newer version, pip does not seem to upgrade a dependency when installing through git commit.How to Reproduce
Run:
Expected behavior
The first install command installs Sloth version 2.0.5 as a dependency. I would expect that the second install command installs Sloth version 2.0.6. But it does not.
(Note: it does not installs even if I use just
--upgrade
, without--upgrade-strategy only-if-needed
.)Output
The problematic line is:
Pip does notice the old version (2.0.5) but it does not do anything, even if
setup.py
to which git is pointing has version 2.0.6.The text was updated successfully, but these errors were encountered: