Disable pip upgrades temporarily #236
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I think the problem is that the modules were originally installed as sudo and it used to silently fail before (and the code would try normal user first and then sudo). Since the modules are only upgraded on EC2 and GCE and both images were installed as sudo I changed the code to only update using sudo and I believe it is working now (testing a fresh image now to be sure). |
|
Oh, nice! Thanks Pat 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
So #235 didn't seem to fix anything. In the mean time, I wonder if it's better to use flat-out disable the pip upgrades? At least until there's a resolution to pypa/pip#6169.