From: R. David Murray <rdmurray@bitdance.com>
Date: Tue, 3 Nov 2009 14:31:53 +0000 (+0000)
Subject: It turns out test_curses can fail in a 2.6 buildbot because stdout is not
X-Git-Tag: v2.6.5rc1~384
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=24b19992d262ba13a41ecab8948fd9e0b102b0b2;p=python

It turns out test_curses can fail in a 2.6 buildbot because stdout is not
a tty in certain cases.

Merged revisions 75518 via svnmerge from
svn+ssh://pythondev@svn.python.org/python/trunk

........
  r75518 | r.david.murray | 2009-10-19 12:01:28 -0400 (Mon, 19 Oct 2009) | 3 lines

  Only run test_curses when sys.__stdout__ is a tty.  This eliminates the
  last false positive when running regrtest with -j.
........
---

diff --git a/Lib/test/test_curses.py b/Lib/test/test_curses.py
index d1b80f88dc..61f9ca81fc 100644
--- a/Lib/test/test_curses.py
+++ b/Lib/test/test_curses.py
@@ -269,6 +269,8 @@ if __name__ == '__main__':
     curses.wrapper(main)
     unit_tests()
 else:
+    if not sys.__stdout__.isatty():
+        raise unittest.SkipTest("sys.__stdout__ is not a tty")
     # testing setupterm() inside initscr/endwin
     # causes terminal breakage
     curses.setupterm(fd=sys.__stdout__.fileno())