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
As of now, wasabi just calls print(), which by default prints to the stdout. In my opinion, this is wrong, as stdout (in the Unix ideology) should be used to output the result of the program (for eventual piping), while stderr should be used for warnings and errors.
I propose adding a "stream" parameter to Printer.__init__(), which by default should be set to sys.stderr. You can then use it inside the print() call.
If you're low on free time, I can implement this, too :)
The text was updated successfully, but these errors were encountered:
My feeling is that it's fine to make it more configurable, but for our current use of wasabi it makes sense for the default to stay stdout. In many cases, the warnings and errors from wasabi are the actual output. (Whether you could argue that some of the current warnings in CLI commands could be python warnings instead is a separate issue.)
As of now, wasabi just calls
print()
, which by default prints to the stdout. In my opinion, this is wrong, as stdout (in the Unix ideology) should be used to output the result of the program (for eventual piping), while stderr should be used for warnings and errors.I propose adding a "stream" parameter to
Printer.__init__()
, which by default should be set tosys.stderr
. You can then use it inside theprint()
call.If you're low on free time, I can implement this, too :)
The text was updated successfully, but these errors were encountered: