Work around the mising RECORD file with homebrew pip. #14556
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 the last week or so, all macOS CI builds have been failing because of an issue with a recent Homebrew update.
The packaged version of
pip25.0.1 installed by homebrew doesn't include aRECORDfile in the distribution metadata. As a result, any attempt to upgradepipfails, because pip can't uninstall itself.As a workaround to get CI unstuck, this writes a dummy RECORD file so that pip can be upgraded. This does leave a stray
pip-25.0.1.dist-infofolder after thepipupgrade... but at least CI can run.The Homebrew documented workaround is to specify
--force-reinstall; this doesn't work - again, because the existing version of pip can't be uninstalled.Deleting the existing pip version can't work either, because without pip, you can't install pip.