cli: add devnull fallback for missing stdout fd #6197
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.
Follow-up of #6142
This fixes the case where
sys.stdout
isNone
, when the Python process doesn't have the stdout file descriptor (fd1). This can be forced in BASH for example, by appending>&-
.Currently on master, this results in an
AttributeError
, as thestreamlink_cli.compat
module assigns itsstdout
attribute tosys.stdout.buffer
, the binary output stream used for writing stream content to stdout (e.g.--stdout
).So when fd1 is missing and
sys.stdout is None
, we need a fallback stream. Simply use a devnull output stream in this case (and close it on exit).When stdout is missing, the logging stream and console output stream will automatically be stderr.
master
PR
Removing stderr as well is currently unsupported, and the process will stop because of a failure of the logging / console output setup, which falls back to stderr if stdout is None. Maybe I'll have a look at this later, too.