From: R. David Murray <rdmurray@bitdance.com>
Date: Mon, 19 Oct 2009 16:04:44 +0000 (+0000)
Subject: Note that on py3k we are actually looking at sys.stdout, not sys.__stdout__.
X-Git-Tag: v3.2a1~2372
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=09386446850b0ce3a5d59ff24ba4ccc3efd14a2b;p=python

Note that on py3k we are actually looking at sys.stdout, not sys.__stdout__.

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 2615ffb1cb..9273ba8311 100644
--- a/Lib/test/test_curses.py
+++ b/Lib/test/test_curses.py
@@ -275,6 +275,8 @@ def main(stdscr):
         curses.resetty()
 
 def test_main():
+    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())