From ba9c6dc51c6dc0dca67944bf859802389bcaba9b Mon Sep 17 00:00:00 2001 From: =?utf8?q?Karl=20Hasselstr=C3=B6m?= Date: Thu, 16 Nov 2006 19:45:28 +0000 Subject: [PATCH] Print progress message to stderr, not stdout MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit Printing progress messages to stdout causes them to get mixed up with the actual output of the program. Using stderr is much better, since the user can then redirect the two components separately. Signed-off-by: Karl Hasselström Signed-off-by: Catalin Marinas --- stgit/git.py | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/stgit/git.py b/stgit/git.py index 20cac61..0e83ffc 100644 --- a/stgit/git.py +++ b/stgit/git.py @@ -186,8 +186,9 @@ def __tree_status(files = None, tree_id = 'HEAD', unknown = False, """Returns a list of pairs - [status, filename] """ if verbose: - print 'Checking for changes in the working directory...', - sys.stdout.flush() + print >> sys.stderr, \ + 'Checking for changes in the working directory...', + sys.stderr.flush() refresh_index() @@ -226,7 +227,7 @@ def __tree_status(files = None, tree_id = 'HEAD', unknown = False, cache_files.append(fs) if verbose: - print 'done' + print >> sys.stderr, 'done' return cache_files -- 2.11.0