From: Benjamin Peterson <benjamin@python.org>
Date: Sun, 29 Mar 2009 21:22:35 +0000 (+0000)
Subject: this has been fixed since 2.6 (I love removing these)
X-Git-Tag: v2.7a1~1758
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=d2c184605e78d9eaf18a6ce83e4ac922bdd18057;p=python

this has been fixed since 2.6 (I love removing these)
---

diff --git a/Lib/test/crashers/multithreaded_close.py b/Lib/test/crashers/multithreaded_close.py
deleted file mode 100644
index 52243414d6..0000000000
--- a/Lib/test/crashers/multithreaded_close.py
+++ /dev/null
@@ -1,14 +0,0 @@
-# f.close() is not thread-safe: calling it at the same time as another
-# operation (or another close) on the same file, but done from another
-# thread, causes crashes.  The issue is more complicated than it seems,
-# witness the discussions in:
-#
-# http://bugs.python.org/issue595601
-# http://bugs.python.org/issue815646
-
-import thread
-
-while 1:
-    f = open("multithreaded_close.tmp", "w")
-    thread.start_new_thread(f.close, ())
-    f.close()