What are peoples thoughts on switching to stderr for all log output?
Then we could only use stdout for outputting json from commands that choose to support a —json flag (or potentially other formats for machine parsing that make sense)
We could try and support things like —json in a way that means for those use cases stdout isn’t used, but that’s more complex and potentially more error prone than not using stdout at all.
I’m wondering if a change like this would be considered breaking or not? If the current output is only meant to be human readable and not parsed, then possibly not.
Asking because I’d like a —json flag for page publishing that outputs the url and I’m wondering what direction to go in. I hacked together an approach that switches the logger into an stderr only mode but if we could always use stderr it would become a lot simpler, hence this issue :)
refs #2927
refs #2437
What are peoples thoughts on switching to stderr for all log output?
Then we could only use stdout for outputting json from commands that choose to support a
—jsonflag (or potentially other formats for machine parsing that make sense)We could try and support things like
—jsonin a way that means for those use cases stdout isn’t used, but that’s more complex and potentially more error prone than not using stdout at all.I’m wondering if a change like this would be considered breaking or not? If the current output is only meant to be human readable and not parsed, then possibly not.
Asking because I’d like a
—jsonflag for page publishing that outputs the url and I’m wondering what direction to go in. I hacked together an approach that switches the logger into an stderr only mode but if we could always use stderr it would become a lot simpler, hence this issue :)refs #2927
refs #2437