From 6a05e8a6061aad6a1fbcad52a9b645a40b7d840c Mon Sep 17 00:00:00 2001 From: Georg Brandl Date: Tue, 18 May 2010 23:47:48 +0000 Subject: [PATCH] Merged revisions 70697 via svnmerge from svn+ssh://pythondev@svn.python.org/python/trunk MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit ........ r70697 | benjamin.peterson | 2009-03-29 21:22:35 +0000 (So, 29 Mär 2009) | 1 line this has been fixed since 2.6 (I love removing these) ........ --- Lib/test/crashers/multithreaded_close.py | 14 -------------- 1 file changed, 14 deletions(-) delete mode 100644 Lib/test/crashers/multithreaded_close.py 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() -- 2.50.0