Handle broken pipe issue #17
Open
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
One of common use-cases is piping the leapp inspector output to another utilis - such as less: $ leapp-inspector messages | less It's annoying to see the broken pipe traceback after closing the application. Fix that for Py2 & Py3 to not see this error anymore.
|
Considering that it does not make sense to fix it for Py2. As far as the solution has not impact on py2, I am considering it ok. |
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.
One of common use-cases is piping the leapp inspector output to another utilis - such as less:
$ leapp-inspector messages | less
It's annoying to see the broken
pipe traceback after closing the application. Fix that for Py2 & Py3 to not see this error anymore.
Note
Currently it works just under Py3. Py2 is still broken.