From: Karl Hasselström Date: Thu, 16 Nov 2006 19:45:28 +0000 (+0000) Subject: Print progress message to stderr, not stdout X-Git-Tag: v0.14.3~425 X-Git-Url: https://git.distorted.org.uk/~mdw/stgit/commitdiff_plain/ba9c6dc51c6dc0dca67944bf859802389bcaba9b?hp=6f6d039f0cfb7470d11f77cacb8612b1b4ed40d1 Print progress message to stderr, not stdout 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 --- 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