<div dir="ltr">Here's the link to the code review: <a href="https://review.openstack.org/#/c/147399/">https://review.openstack.org/#/c/147399/</a><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 4, 2015 at 7:17 AM, Dolph Mathews <span dir="ltr"><<a href="mailto:dolph.mathews@gmail.com" target="_blank">dolph.mathews@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class=""><br><br>On Wednesday, March 4, 2015, David Stanek <<a href="mailto:dstanek@dstanek.com" target="_blank">dstanek@dstanek.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 4, 2015 at 6:50 AM, Abhishek Talwar/HYD/TCS <span dir="ltr"><<a>abhishek.talwar@tcs.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">While working on a bug for keystoneclient I have replaced sys.exit with return. However, the code reviewers want that the output should be on stderr(as sys.exit does). So how can we get the output on stderr.</blockquote></div><br>The print function allows you to specify a file:</div><div class="gmail_extra"><br></div><div class="gmail_extra">    >>> from __future__ import print_function<br></div><div class="gmail_extra"><div class="gmail_extra">    >>> import sys<br></div><div class="gmail_extra"></div></div><div class="gmail_extra"><div class="gmail_extra">    >>> print('something to', file=sys.stderr)</div><br clear="all"><div>The __future__ import is needed for Python 2.6/2.7 because print was changed to a function in Python 3.</div></div></div></blockquote><div><br></div></span><div>I hope that answers your question. Can we have a link to the bug and/or code review?</div><div class=""><div class="h5"><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div><br></div><div><br></div>-- <br><div>David<br>blog: <a href="http://www.traceback.org" target="_blank">http://www.traceback.org</a><br>twitter: <a href="http://twitter.com/dstanek" target="_blank">http://twitter.com/dstanek</a><div>www: <a href="http://dstanek.com" target="_blank">http://dstanek.com</a></div></div>
</div></div>
</blockquote>
</div></div><br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>