]> granicus.if.org Git - python/commitdiff
Merged revisions 70697 via svnmerge from
authorGeorg Brandl <georg@python.org>
Tue, 18 May 2010 23:47:48 +0000 (23:47 +0000)
committerGeorg Brandl <georg@python.org>
Tue, 18 May 2010 23:47:48 +0000 (23:47 +0000)
svn+ssh://pythondev@svn.python.org/python/trunk

........
  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 [deleted file]

diff --git a/Lib/test/crashers/multithreaded_close.py b/Lib/test/crashers/multithreaded_close.py
deleted file mode 100644 (file)
index 5224341..0000000
+++ /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()