-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
ci: pip: use installed version #6522
Conversation
It's already been reported to pip: pypa/pip#7620 |
.github/workflows/main.yml
Outdated
@@ -122,7 +122,7 @@ jobs: | |||
python-version: ${{ matrix.python }} | |||
- name: Install dependencies | |||
run: | | |||
python -m pip install --upgrade pip | |||
python -m pip install --upgrade "pip<20" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I expect 20.0.1 will be out with a fix soonish, how about?
python -m pip install --upgrade "pip<20" | |
python -m pip install --upgrade "pip!=20.0.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm more in favor to pinning it to some exact version instead: we should not get disrupted by issues through it, but rather bump it from time to time when feasible - it's just disruptive if it breaks suddenly.
Upgrading pip unnecessarily can be disruptive, e.g. when pip 20 breaks [1]. This makes it more predictable, and a bit faster also. 1: pypa/pip#7620
Amended to just use the installed version. |
I think upgrading pip is a good idea - and it looks like pip 20.0.1 fixing this is out already. |
Why? |
Often, CI environments do have quite outdated versions of pip (admittedly, I'm not sure about GitHub Actions though) - to the point where dependencies are non-installable or a wrong version is installed. One example that comes to mind is platform / python_version markers; another more recent one is manylinux2014 wheels. |
@The-Compiler I see, but as can be seen here our image is fine. |
@nicoddemus please approve, or close it. |
Closing then, as in general it is recommended to always upgrade Of course this opens up the possibility of a pip upgrade being broken, but this is very very rare and usually fixed in hours, because it usually blows up the world. |
* ci: use installed pip, upgrade to pinned if necessary Ref: pytest-dev#6522 * PIP_DISABLE_PIP_VERSION_CHECK=1
Just for reference: I've fixed Travis CI (for 3.5.1 though) two (or three) times now since then, which was caused due to package upgrades. |
Currently fails with:
Ref: https://github.com/pytest-dev/pytest/runs/400730404