When logging to the console, we should use stderr

Registered by Ian Cordasco

As noted on https://review.openstack.org/#/c/167522/1/bandit/bandit.py, when we're logging to the console, we should choose to log to stderr instead of stdout. This allows users to collect the logging separately from the generated output. In the case of the review, when generating logs and formatting the output as JSON, we likely still want logging information but we don't want it breaking the JSON format. In this case if we defaulted to logging to stderr (instead of stdout), the tool could still be used like so:

    $ bandit -f json src/ > output.json

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Ian Cordasco
Direction:
Needs approval
Assignee:
Tim Kelsey
Definition:
Obsolete
Series goal:
None
Implementation:
Started
Milestone target:
None
Started by
Tim Kelsey
Completed by
Eric Brown

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/log-to-stderr,n,z

Addressed by: https://review.openstack.org/257470
    Move status counter to stderr

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.