Temporarily use --no-cache-dir for pip on mingw32 #3175
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For #3156.
mingw32 builds fail like this:
https://ci.appveyor.com/project/Python-pillow/pillow/build/3763/job/kx8amjf3srp21560
This looks like this is caused by a caching bug in a vendored dependency of pip 10 (pypa/pip#5250), which already has a released fix (psf/cachecontrol#190).
The next pip 18 (yes, 18, they've switched to CalVer) is due for release in July (pypa/pip#5324)
In the meantime, let's skip pip caching for this particular job to get the CI back to green.
Changes proposed in this pull request:
pip
with--no-cache-dir
for mingw32Let's keep #3156 open so we remember to revert this when pip 18 is out.