diff options
| author | Georg Brandl <georg@python.org> | 2010-05-18 23:47:48 +0000 |
|---|---|---|
| committer | Georg Brandl <georg@python.org> | 2010-05-18 23:47:48 +0000 |
| commit | 6a05e8a6061aad6a1fbcad52a9b645a40b7d840c (patch) | |
| tree | c5f9e1a8664527c62090fca9a9b026c08b39ac74 | |
| parent | 5473410ee7038c322a34e0bf95b0f62b34659583 (diff) | |
| download | cpython-git-6a05e8a6061aad6a1fbcad52a9b645a40b7d840c.tar.gz | |
Merged revisions 70697 via svnmerge from
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)
........
| -rw-r--r-- | Lib/test/crashers/multithreaded_close.py | 14 |
1 files changed, 0 insertions, 14 deletions
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() |