Ignore stderr message #30
Merged
Conversation
This file contains hidden or 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
|
Current workaround would be to create your own Dockerfile. Assuming you're on Python3: The file should look like then run: |
|
I understand the workaround and also my fix is just a temporary fix, but if user have to or decide to use the default docker image, it should still be able to deploy and that's what this PR about. I don't think a pip upgrade warning should prevent user from deployment. |
|
+1 on ignoring this issue. Really shouldn't be something that breaks the deploy, maybe a warning though? |
|
+1 |
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.
pip just upgraded to 9.0.2 and a new available pip version will produce warning messages. For people that used default docker settings on lamcli/lambda (where docker image is still using pip 9.0.1), the change is required for successful deployment.