From: Neal Norwitz <nnorwitz@gmail.com>
Date: Mon, 3 Apr 2006 05:27:05 +0000 (+0000)
Subject: Skip the test for sys.stdin.seek(-1) on OSF/1 (Tru64) since it does Bad Things
X-Git-Tag: v2.5a1~63
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=9cdfa4c98cd093d37450e1e6b025fc3aa8d50fe1;p=python

Skip the test for sys.stdin.seek(-1) on OSF/1 (Tru64) since it does Bad Things
like cause the interpreter to exit abruptly.  If there's a way to fix this,
it would be good to really fix it.  It could just be the operation of the
std C library and we just aren't supposed to do that.

When the test case is skipped, we print a message so the user can check
for themselves.
---

diff --git a/Lib/test/test_file.py b/Lib/test/test_file.py
index efb06f44e4..a9f5e4677b 100644
--- a/Lib/test/test_file.py
+++ b/Lib/test/test_file.py
@@ -100,12 +100,18 @@ else:
     print "writelines accepted sequence of non-string objects"
 f.close()
 
-try:
-    sys.stdin.seek(-1)
-except IOError:
-    pass
+# This causes the interpreter to exit on OSF1 v5.1.
+if sys.platform != 'osf1V5':
+    try:
+        sys.stdin.seek(-1)
+    except IOError:
+        pass
+    else:
+        print "should not be able to seek on sys.stdin"
 else:
-    print "should not be able to seek on sys.stdin"
+    print >>sys.__stdout__, (
+        '  Skipping sys.stdin.seek(-1), it may crash the interpreter.'
+        ' Test manually.')
 
 try:
     sys.stdin.truncate()