You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the use case of combining a live tail session with grep or other utilities in a pipeline, there should be a separation between the log data going to stdout and all other diagnostic messages going to stderr.
My python is rusty, but I believe this amounts to simply giving a file=sys.stderr kwarg to every call to print() inside of liveTail(), e.g. here.
The text was updated successfully, but these errors were encountered:
This is a good suggestion - thanks. We'll address it in a forthcoming
update.
Cheers,
Steve
On Thu, Nov 10, 2016 at 9:39 AM, Ryan Artecona [email protected]
wrote:
For the use case of combining a live tail session with grep or other
utilities in a pipeline, there should be a separation between the log data
going to stdout and all other diagnostic messages going to stderr.
For the use case of combining a live tail session with grep or other utilities in a pipeline, there should be a separation between the log data going to stdout and all other diagnostic messages going to stderr.
My python is rusty, but I believe this amounts to simply giving a
file=sys.stderr
kwarg to every call toprint()
inside ofliveTail()
, e.g. here.The text was updated successfully, but these errors were encountered: