🐛 FIX: write status messages to sys.stderr #47
Merged
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
writing only the rendered output to stdout allows piping to files / pbcopy with minimal editing
|
Thanks Min! I'm fine with logging as well, have just been prioritizing simple machinery so far and complexifying when necessary |
consideRatio
changed the title
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.
writing only the rendered output to stdout allows piping output to files / pbcopy with minimal editing
I did a previous pass on this in #39. I'm not sure if there's a way to test that no prints to stderr are added? Maybe it would be easier to adopt logging, which also goes to stderr by default and would enable things like log-levels.