From d2c184605e78d9eaf18a6ce83e4ac922bdd18057 Mon Sep 17 00:00:00 2001 From: Benjamin Peterson Date: Sun, 29 Mar 2009 21:22:35 +0000 Subject: [PATCH] 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.1