Change console logging stream from stdout to stderr - #617
Conversation
|
None that I can think of. I was concerned that maybe some Pearson management command tests might care, but it looks like tests pass fine. 👍 |
|
@brianhw yeah, that is why I added you to the PR. Thanks for checking. |
|
This will take effect for code running under gunicorn in nginx. Can you test what it does with the output in that situation? (You should be able to use the virtualbox single stack thing that @jarv has set up to test it). |
|
I checked on the vagrant/virtualbox setup. The change does not affect the upstart logs @cpennington Is there something else you think I should check? |
|
@rocha there's nothing that I can think of from a jenkins/test perspective. 👍 |
|
Sounds like the right set of places. 👍 |
Change console logging stream from stdout to stderr
…swer Added styles for detailed solution
Updated hash code for group-project-v2
…ration_phase1 Add ga_operation tool's function which move video files between AWS S3 buckets. openedx#617
…ration_p1_2 Add ga_operation tool's function which create certificate and publish openedx#617
…ration_p1_set_sender Fix to be able to specify the mail sender to environment file for ga_operation tools. openedx#617
…ration_p1_show_cert_status Modify web browser on the result message of publish certificate from ga_operation tools. openedx#617
…ration_p2 Add aggregate function for ga_operation tools openedx#617
…ongo_settings Mod ga_operation mongo settings which move from env file to auth file openedx#617
…ration_phase3 Add specific aggregation function for ga_operation tools openedx#617
Having the root logger send its output to stdout makes it hard to have django management commands that produce output that can be consumed by shell commands.
@cpennington @jzoldak @brianhw @jarv
any unintented consequence of this change?