-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
log to stderr instead of stdout #8886
Conversation
Welcome, new contributor! Please make sure you've read our contributing guide and we look forward to reviewing your pull request shortly ✨ |
I only checked on Windows, but the change is trivial and should work on Linux & macOS. If there is a better term than "desktop targets" I will edit the changelog to use it instead. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems like a better solution, and the motivation in the linked issue is good. Let's see if anyone chimes in with an argument not to do this.
It looks like your PR is a breaking change, but you didn't provide a migration guide. Could you add some context on what users should update when this change get released in a new version of Bevy? |
Would a migration section in the PR be appropriate? |
Yeah, a tiny migration guide would be helpful still to point users in the right direction :) |
Objective
bevy_log
writes logs tostdout
(with ANSI formatting), which gets in the way with program output and complicates parsing.Solution
bevy_log
to write tostderr
instead ofstdout
Changelog
Changed:
stderr
rather thanstdout
on desktop targetsMigration Guide
stderr
instead of fromstdout
2> output.log
on the command line to savestderr
to a file