From: Neal Norwitz <nnorwitz@gmail.com>
Date: Sun, 27 Jan 2008 18:09:48 +0000 (+0000)
Subject: Update the comment and remove the close.  If we close we can't flush anymore.
X-Git-Tag: v2.6a1~363
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=c5198090f3c1a3d40710a03707c62884234f0e6a;p=python

Update the comment and remove the close.  If we close we can't flush anymore.
We might still need to close after the for loop if flushing 6! times still
doesn't cause the signal/exception.
---

diff --git a/Lib/test/test_resource.py b/Lib/test/test_resource.py
index 496259f632..225f88278d 100644
--- a/Lib/test/test_resource.py
+++ b/Lib/test/test_resource.py
@@ -56,13 +56,12 @@ class ResourceTest(unittest.TestCase):
                         f.flush()
                         # On some systems (e.g., Ubuntu on hppa) the flush()
                         # doesn't always cause the exception, but the close()
-                        # does eventually.  Try closing several times in
+                        # does eventually.  Try flushing several times in
                         # an attempt to ensure the file is really synced and
                         # the exception raised.
                         for i in range(5):
                             time.sleep(.1)
                             f.flush()
-                            f.close()
                     except IOError:
                         if not limit_set:
                             raise