Re: [openstack-dev] [keystone] Output on stderr

2015-03-04 Thread Lin Hua Cheng
Here's the link to the code review: https://review.openstack.org/#/c/147399/ On Wed, Mar 4, 2015 at 7:17 AM, Dolph Mathews wrote: > > > On Wednesday, March 4, 2015, David Stanek wrote: > >> >> On Wed, Mar 4, 2015 at 6:50 AM, Abhishek Talwar/HYD/TCS < >> abhishek.tal...@tcs.com> wrote: >> >>> Wh

Re: [openstack-dev] [keystone] Output on stderr

2015-03-04 Thread Dolph Mathews
On Wednesday, March 4, 2015, David Stanek wrote: > > On Wed, Mar 4, 2015 at 6:50 AM, Abhishek Talwar/HYD/TCS < > abhishek.tal...@tcs.com > > wrote: > >> 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

Re: [openstack-dev] [keystone] Output on stderr

2015-03-04 Thread David Stanek
On Wed, Mar 4, 2015 at 6:50 AM, Abhishek Talwar/HYD/TCS < abhishek.tal...@tcs.com> wrote: > 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 st

[openstack-dev] [keystone] Output on stderr

2015-03-04 Thread Abhishek Talwar/HYD/TCS
Hi All, 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. def do_user_password_update(kc, args): """Update user password.""" user