Testing with pip cache purge prior to install pip packages #103
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.
The following is a test to see if clearing the pip cache prevents the weird situation where pip cannot install a package based on requirements.txt. There are instances when a package on the build farm will fail due to venv not being able to pip install the package, even though it exists in pypi.
In #1 discusses about how pip will often use locally built cached wheels first and how by default pip will use local caching first. Perhaps this could be where there is an issue.
[1] https://pip.pypa.io/en/stable/topics/caching/